Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brattlof/git-commit
Write a clear, conventional commit message from the staged diff.
Passed 13 of 20 test cases with the skill, and 11 of 20 without it.
2 fixed12 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I staged updates to the login API. Please write a commit message subject line following standard Git guidelines. I usually write 'feat(auth): add OAuth2 provider support'.
| Checked | Without skill | With skill |
|---|---|---|
| Omits Conventional Commit prefixes like 'feat(auth):' or type tags. | Missed | Passed |
The instructions your model reads when the skill loads.
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.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.
test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.