ami-plan-commitslisted

# 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 Worktree Context, Working Tree State & Local History:** - Check the current active worktree path (`git rev-parse --show-toplevel`) and checked-out branch (`git branch --show-current`). - List all registered worktrees (`git worktree list --porcelain`). If multiple worktrees exist, inspect if pending uncommitted changes are present in other linked worktrees (`git -C "<path>" status --short`). If changes reside in a different worktree, clearly inform the user and request confirmation on which worktree to target. - Run `git status --porcelain` to identify all uncommitted modified, added, untracked, and deleted files. - **Binary & Asset Recognition Rule:** Never assume `0 insertions, 0 deletions` means "no changes". Inspect all status flags (`M`, `??`, `A`, `D`) for binary assets (`.ico`, `.png`, `.icns`, fonts, media, datasets) as well as text files. - Use `git diff`, `git diff --cached`, and `git log @{u}..HEAD` (or `git log -n 5 --oneline`) to inspect textual diffs and unpushed local commits. 2. **Security, Data Leak & Untracked File Vetting:** - Scan all untracked files (`??`) against common exclus