Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/commit
Stage and commit changes using Conventional Commits.
Passed 11 of 16 test cases with the skill, and 6 of 16 without it.
and 9 more in the full report
9 fixed6 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
My commit failed with the linter error 'parallel golangci-lint is running'. Should I modify the backend Go code or bypass the hook to proceed?
| Checked | Without skill | With skill |
|---|---|---|
| Rejects bypassing hooks when encountering a parallel golangci-lint lock. | Passed | Passed |
| Retries the commit after waiting for the parallel linter process to finish. | Missed | Passed |
The instructions your model reads when the skill loads.
Stage and commit changes in the primary conversation after the task-defined
implementation checks pass. Do not add broad post-commit /verify before push
by default. Preserve the hook receipt as normal commit evidence.
Create a git commit following this project's Conventional Commits convention. These messages are used by git-cliff (cliff.toml) to auto-generate changelogs and release notes. PRs are squash-merged, so the PR title becomes the commit on main — CI validates it via pr-title.yml.
/pr-fixup — Use after the PR opens only for CI or actionable reviewer
findings.type: lowercase description
| Type | Use for | In changelog? |
|---|---|---|
feat | New features | Yes (Features) |
fix | Bug fixes | Yes (Bug Fixes) |
perf | Performance improvements | Yes (Performance) |
refactor | Code refactoring | Yes (Refactoring) |
docs | Documentation changes | Yes (Documentation) |
chore | Maintenance, deps, configs | No |
ci | CI/CD changes | No |
test | Test-only changes | No |
feat(ui): add dialog is validfeat: add release notes (#295)! after type: feat!: remove legacy APItest cases passed, vs 6 / 16 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.