Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Write a clear, conventional commit message from the staged diff.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | 0% | 0% |
| case-16 | ✗→✓ | ▲ Improved | -53% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 1% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -10% | 0% |
| case-06 | ✓→✓ | = Same ✓ | -3% | 0% |
Use this when the user asks you to commit staged changes and wants a well-formed message.
git diff --cached to see exactly what is staged.trailing period (for example "Add retry to the upload client").
changed and why, wrapped at 72 columns.
git commit only after the user confirms.Describe what the diff actually does, not what was intended. Keep one logical change per commit; if the subject needs the word "and", the commit is probably too big.
Other measured skills in the registry, with their headline benchmark lift.