| name | atomic-commit |
| description | Analyzes git working tree and creates atomic commits with proper messages. Use when the user asks to commit changes, wants atomic commits, or mentions cleaning up their git history before pushing. |
| allowed-tools | Bash, Read |
Atomic Commit Skill
When to Activate
Activate when the user:
- Asks to commit their changes
- Mentions "atomic commits" or splitting commits
- Wants to clean up changes before pushing
- Has multiple unrelated changes to commit
Process
1. Analyze Working Tree
git status
git diff --stat
git diff --cached --stat
2. Group Changes
Identify logical groupings:
- By feature/fix: Related changes across files
- By file type: Config changes, test updates, docs
- By scope: Single module or component changes
3. Create Atomic Commits
For each logical group:
- Stage only the relevant files:
git add <specific-files> - Commit with a descriptive message
- Repeat for remaining changes
Commit Message Format
<type>: <concise description>
<optional body explaining why, not what>
🤖 Generated with Claude Code
Co-Authored-By: <model> <noreply@anthropic.com>
Types: feat, fix, refactor, docs, test, chore, style
Rules
- Never use
git add .orgit add -Afor atomic commits - Each commit should be independently buildable when possible
- Ask user before committing if grouping is ambiguous
- Show proposed commit plan before executing
- Never force push or amend without explicit permission