ami-commit-plannerlisted

# Skill: Commit Planner When this skill is invoked (either by the user or by an agent), you must act as a Git Commit Strategist. Your goal is to group related changes into meaningful commits and propose a clear and concise commit plan to the user for approval. Clear commits makes it easier to find regressions and revert unwanted changes. ## Workflow 1. **Analyze Working Tree & Local History:** Use git commands (`git status`, `git diff`, `git diff --cached`, and `git log @{u}..HEAD` or `git log -n 5 --oneline`) to identify all uncommitted modified/new/deleted files and review recently created unpushed commits. 2. **Security & Data Leak Audit:** Actively scan all diffs and uncommitted files to ensure no sensitive data (API keys, secrets, passwords, tokens, PII) is being committed. If any leak is detected, **ABORT** the process immediately, alert the user, and refuse to stage or commit the sensitive files. 3. **Structure & Group Changes:** Carefully analyze the modifications and group them into logical, distinct commits. Avoid lumping unrelated changes into a single monolithic commit. Consider the following grouping strategies: - **Amend Strategy:** If the current uncommitted work consists of minor fixes, typos, or additions to the most recent **unpushed** commit, propose amending it (`git commit --amend`) instead of adding a redundant commit. - **Squash / Consolidation Strategy:** If there are multiple unpushed local commits that represent iterative WIP or fragmented fi