Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/commit
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references.
Passed 16 of 20 test cases with the skill, and 10 of 20 without it.
and 4 more in the full report
6 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft a commit footer linking to Linear ticket LINEAR-SEC-99 without automatically closing the ticket when merged.
| Checked | Without skill | With skill |
|---|---|---|
| Uses `Refs LINEAR-SEC-99` in the commit footer | Missed | Passed |
| Selects the non-closing reference keyword for Linear tickets | Passed | Passed |
The instructions your model reads when the skill loads.
Follow these conventions when creating commits for Sentry projects.
main or master.Before committing, always check the current branch:
git branch --show-current
If you're on main or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation. The create-branch skill will still propose a branch name for the user to confirm.
Use the create-branch skill to create the branch. After create-branch completes, verify the current branch has changed before proceeding:
git branch --show-current
If still on main or master (e.g., the user aborted branch creation), stop — do not commit.
<type>(<scope>): <subject>
<body>
<footer>
The header is required. Scope is optional. All lines must stay under 100 characters.
test cases passed, vs 10 / 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.