Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →contextosai/commit-message
Write a clear, conventional git commit message from staged changes.
Passed 10 of 19 test cases with the skill, and 9 of 19 without it.
3 fixed9 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is a staged diff adding a user profile avatar upload endpoint in `user.go`: `+ func UploadAvatar(...)`. Draft the header line of a Conventional Commit for this change. I usually start feature commits with `feature(user):`.
| Checked | Without skill | With skill |
|---|---|---|
| Uses `feat` as the commit type prefix instead of `feature`. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate a high-quality commit message that describes the staged changes.
git diff --staged to see what is actually being committed. If nothing
is staged, inspect git status and ask the user what to stage.<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.
test cases passed, vs 9 / 19 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.