← ClaudeAtlas

commitlisted

Use when the user asks to inspect changes, split work into logical commits, stage hunks, or create commits. Plan every requested repository and execute the complete commit run in the same response.
mikaeltorni/programming_prompts · ★ 1 · Code & Development · score 74
Install: claude install-skill mikaeltorni/programming_prompts
# Commit skill Create small, reviewable conventional commits from the requested worktree(s). ## Workflow 1. Inspect every requested repository before staging: ```bash git rev-parse HEAD git status --short git diff --stat git diff --staged --stat git diff git diff --staged git ls-files --others --exclude-standard ``` Read relevant untracked files. If anything is already staged, rebuild the index with `git restore --staged -- :/` and inspect again. 2. Print a numbered plan covering every changed hunk. Group by purpose, not by filename. Keep implementation, its focused tests, and required docs or installer changes together. Mark mixed files as `partial`. 3. Start plan item 1 immediately. The plan is not an approval checkpoint. Never ask whether to proceed or wait for confirmation. 4. Stage only the current group. Use exact paths or interactive patch mode: ```bash git add -- path/to/file git add -p -- path/to/mixed_file ``` Never use `git add .`, `git add -A`, `git add -u`, or stage a whole mixed file. Check the staged and unstaged sides after partial staging. 5. Before committing, verify: ```bash git diff --staged --name-status git diff --staged --stat git diff --staged --check git status --short ``` Confirm that every staged hunk belongs to this plan item, every staged test has its implementation, and later groups remain unstaged. 6. Validate the staged snapshot, not the dirty work