Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 89% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 30% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -8% | 0% |
| case-22 | ✓→✗ | ▼ Worse | 4% | 0% |
| case-20 | ✓→✓ | = Same ✓ | -17% | 0% |
Generate a high-quality commit message that describes the staged changes.
git diff --staged to see what is actually being committed. If nothingis staged, inspect git status and ask the user what to stage.
one unrelated thing, suggest splitting it into multiple commits.
<type>(<optional scope>): <subject>
<body — what changed and why, wrapped at ~72 cols>feat, fix, refactor, docs, test, chore, perf,build, ci.
feat(auth): add refresh-token rotation
Tokens are now rotated on every refresh so a leaked token is valid for
at most one cycle.fix(parser): handle empty input without panickingOther measured skills in the registry, with their headline benchmark lift.