Commit each
npx -y skills add dkmqflx/claude-tools --skill commit-eachAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Split the current git changes (working tree + staged) into one commit per logical unit of work. Use when the user asks to commit changes separately by task — phrases like "각각 커밋해줘", "작업별로 커밋", "변경사항 분리해서 커밋", "split commits", "commit by task", "/commit-each".
SKILL.md
2.2 KB, 468 tokens by cl100k_base, as published. Nobody here has run it
Commit Each
Group the current changes into logical units and create one commit per unit.
When to apply
User asks to commit the current diff as several separate commits, one per task / concern. Do not apply when the user wants a single bundled commit, or when there are no changes.
Process
- Survey — run in parallel:
git status(untracked + modified)git diff(unstaged)git diff --staged(staged)git log --oneline -10(message style reference)
- Group the changes by logical unit:
- Different feature / skill / command / module → separate commits.
- A new file and its tests → usually one commit.
- Refactor + unrelated bugfix mixed inside one file → flag to user; do not auto-split with
git add -p. - Pure formatting-only changes → separate commit at the end.
- Confirm grouping with the user when ambiguous (≥ 3 groups, or any mixed-purpose file). For obvious splits (clearly different directories or unrelated files), proceed without asking.
- Commit each group sequentially:
- Stage only that group's files by name — never
git add ./-A/-u. - Match the repo's existing message style (check
git log -10; current convention here is lowercase imperative). - Use HEREDOC for multi-line messages.
- Always end with
Co-Authored-By: Claude Opus 4.7 <[email protected]>.
- Stage only that group's files by name — never
- Verify with a final
git status— clean, or containing only what the user explicitly excluded.
Guardrails
- Never stage with
git add ./-A/-u— list files explicitly. - Never commit files that look like secrets (
.env,credentials*, keys). Warn instead. - Never amend or rewrite existing commits — always create new ones.
- Never bundle unrelated work to "save a commit."
- If a pre-commit hook fails, fix the underlying issue and create a NEW commit — never use
--no-verify.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.