Atomic Commit helps create clean, atomic commits by analyzing changes, detecting mixed concerns, and ensuring each commit is a complete unit of work...
Standalone skill for non-TDD workflows. Helps create clean, atomic commits by analyzing changes and detecting mixed concerns.
git status && git diff && git diff --staged
Look for files mixing:
Group files by shared purpose. Present grouping to user for confirmation.
Example:
Group 1: "Add user auth" → auth/login.ts, auth/session.ts, tests/auth/login.test.ts
Group 2: "Fix password validation" → validators/password.ts, tests/validators/password.test.ts
For each group:
git add <file1> <file2> (NO git add .)git diff --stagedgit log -1 --onelineConventional commit types: feat|fix|refactor|docs|test|chore|perf|style
git log --oneline -n <N>
gh issue create or glab issue create"feat: description (#42)"DO: One logical change, include related tests, run tests, clear messages, issue numbers DON'T: Mix features/fixes/refactors, commit broken code, vague messages, debug code
☐ Analyze: git status/diff ☐ Identify file purposes ☐ Detect mixed concerns ☐ Group into atomic commits ☐ Confirm with user ☐ For each: stage → review → test → build → commit → verify ☐ Final review
Use when user says: "atomic", "clean commits", "break down commits", "split commits" DO NOT use for TDD workflows (use TDG skill).
"Created N atomic commits. Tests pass. Would you like to review history, push, or create PR?"