skills/custom/git-atomic-commit/SKILL.md
Generates atomic Git commits — each capturing exactly one logical change — formatted as Conventional Commits that match the project's style. Use when the user has multiple files or concerns to commit. For a single-file, single-concern change, write one Conventional Commit directly.
npx skillsauth add rockcookies/skills git-atomic-commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Split a changeset into atomic commits, one change each, and write Conventional Commits.
| Staged | Unstaged | Mode | |--------|----------|------| | ✅ Has changes | — | Direct: commit staged immediately | | ❌ Empty | ✅ Has changes | Plan: output a staging plan, wait for confirmation | | ❌ Empty | ❌ Empty | Exit: "Nothing to commit, working tree clean" |
git status --short
git diff --staged --name-only
git diff --name-only
git log -30 --pretty=format:"%s"
Completion: the 30 most recent commit messages are visible for style detection.
Scan the 30 commits for the project's convention. Prefer Conventional Commits; adapt when the project uses a different format.
Assign every changed file to exactly one group. Split across groups when files:
Each group must pass the reversibility test: reverting this commit alone leaves the others intact.
Format: <type>(<scope>): <subject>
feat, fix, docs, style, refactor, perf, test, build, ci, chorefeat!: or feat(api)!:Direct mode — present, then execute:
=== Commit Plan ===
[1/2] feat(auth): add login validation
- src/auth/validator.ts (modified)
- src/auth/types.ts (new)
[2/2] test(auth): add validator unit tests
- tests/auth/validator.test.ts (new)
Plan mode — present and wait for explicit confirmation before touching anything:
=== Staging Plan ===
[1/2] feat(auth): add login validation
- src/auth/validator.ts
- src/auth/types.ts
[2/2] test(auth): add validator unit tests
- tests/auth/validator.test.ts
Proceed with commits? [y/n]
Completion: every group has its own commit.
tools
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
tools
Teach the user a new skill or concept, within this workspace.
development
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
documentation
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.