Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/commit
Helps write conventional commit messages, create atomic commits, and follow git best practices.
Passed 25 of 25 test cases with the skill, and 14 of 25 without it.
and 8 more in the full report
11 fixed14 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am updating the LICENSE file text to update the copyright year across the Sentry codebase. What commit type prefix applies?
| Checked | Without skill | With skill |
|---|---|---|
| Use license: as the commit type prefix. | Missed | Passed |
The instructions your model reads when the skill loads.
Follow these conventions when creating commits for Sentry projects.
Use this skill when:
Before committing, ensure you're working on a feature branch, not the main branch.
# Check current branch
git branch --show-current
If you're on main or master, create a new branch first:
# Create and switch to a new branch
git checkout -b <type>/<short-description>
Branch naming should follow the pattern: <type>/<short-description> where type matches the commit type (e.g., feat/add-user-auth, fix/null-pointer-error, ref/extract-validation).
<type>(<scope>): <subject>
<body>
<footer>
test cases passed, vs 14 / 25 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.