Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/commit-rules
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
Passed 10 of 17 test cases with the skill, and 7 of 17 without it.
and 2 more in the full report
5 fixed8 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
How many previous commits should be checked when determining the repository commit style before making a new commit?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies inspecting exactly 10 recent commits with git log -n 10 --oneline | Missed | Passed |
The instructions your model reads when the skill loads.
git log -n 10 --oneline.turbo/ content (filenames, acceptance criteria, step numbers, headings) in commit messages. .turbo/ is gitignored, so these references would be opaque to anyone reading without local copies.git commit -m "message" directly—do not use heredoc syntax (sandbox blocks temp file creation)--no-gpg-sign, -c commit.gpgsign=false). If signing fails, use request_user_input to let the user resolve it—they may need to approve a key prompt.test cases passed, vs 7 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.