commit-messagelisted
Install: claude install-skill rgant/claude-plugins
# Commit message
Draft the message. Never stage, commit, or amend. The user signs their own
commits and curates the index by hand.
## Why this skill exists
The rules live in `${CLAUDE_PLUGIN_ROOT}/standards.md` and are often already in
context. They still get missed, because a commit message is written at the end
of a long session and an abstract rule loses to a concrete example sitting
closer in context. The near miss is a read of `git log` "to match the repo's
style". The writer then imitates a message that breaks the rules, and uses that
message to argue past the rule. Older commits predate the rules or were written
before they were enforced.
So: read the rules fresh, read the diff, and check the draft against each rule
before showing it.
## Step 1 — read the rules fresh
Read the "Writing for people" section of `${CLAUDE_PLUGIN_ROOT}/standards.md`.
Then read `${CLAUDE_PLUGIN_ROOT}/guides/commit-messages.md` and
`${CLAUDE_PLUGIN_ROOT}/guides/explanations.md`. Together they are the authority. The checklist
in step 4 comes from them and can lag an edit. If the checklist and the files
disagree, the files win.
Look for a project `CLAUDE.md` too. It can add scope conventions or a PR-base
rule.
## Step 2 — read the diff, not the history
```
git diff --cached --stat # what moved
git diff --cached # what it now says
```
If nothing is staged, say so and ask whether to draft against the working tree
instead. Do not guess.
If the prefix convention of the repo