About prepare-commit
A pre-commit checklist skill for coding agents. It reviews the original task and diff, then runs the documented lint and test checks; it explicitly stops short of committing.
Key features
- 01Revisit the originating issue and code diff
- 02Summarize requested work and changes
- 03Run lint before tests
- 04Stop if either check fails
- 05Never commit or rewrite history
Use cases
- 01Check whether a change addresses its issue
- 02Run project checks before preparing a commit
- 03Review work when no written task exists
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/prepare-commitin Claude Code to confirm it loaded.
Details
From the project READMEPrepare commit
Checklist before a commit. Do not commit. Stop when the checklist is done and wait.
Workflow
Run in this order.
1. Originating artifacts
Re-read the issue, task, or any other artifacts that were the starting point for this conversation, and the code diff.
- Is everything in the issue addressed?
- Summarise the issue and what changes have been made.
- Note if the issue should be closed after committing; if so, you should close the issue once a commit is made.
Where we have made decisions that contradict the issue, update the issue so it reflects what was actually built.
If there is no written starting point, say so and continue.
2. Tests and lint
Prefer the project's documented lint and test entrypoints. Run lint, then tests. Fail-stop on either — do not present the work as ready to commit if either fails.
Don't run a full production build unless the project documents that as the check to use.
Hard rules
- Do not commit, amend or otherwise rewrite history.
- If the user asked to commit, still only prepare. After the checklist, wait for them to confirm.