About commit-changes
A skill that helps developers organize code changes into clear, reviewable Git commits. It guides diff review, commit decomposition, relevant checks, and properly formatted multiline commit messages.
Key features
- 01Review Git status and relevant diffs
- 02Split unrelated work into logical commits
- 03Stage selected hunks and inspect staged diffs
- 04Run relevant checks before committing
- 05Write multiline messages with an AI assistance trailer
Use cases
- 01Separate mixed changes into logical commits
- 02Verify staged content and commit messages before committing
- 03Record skipped checks when applicable
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ tenzir/ skills --skill commit-changesAfter installing, type/commit-changesin Claude Code to confirm it loaded.
Bundled filesreferences/write-commit-messages.md
Details
From the project READMECommit Changes
Commit changes as clean, reviewable snapshots.
Workflow
- Read
gitstatus and the relevant diffs before deciding how many commits to make. - Split orthogonal work into separate logical units. If a file mixes unrelated edits, stage only the hunks for the current commit.
- Run the relevant checks before committing. For Python projects, delegate to
the
follow-python-conventionsskill. If you skip a check, say so. - For each commit:
- Stage only the relevant hunks.
- Read the staged diff before writing the message.
- Write the commit message from what is actually staged, including the AI assistance trailer.
- Create the commit with a real multiline message, using separate
-marguments for subject, body, and final trailer block. - Do not put literal
\nescapes in a single-mstring. - Amend immediately if the final message reads awkwardly.
Comments
Markdown supported