Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/commit-messages
Generates conventional commit messages from staged changes.
Passed 15 of 18 test cases with the skill, and 13 of 18 without it.
3 fixed15 passed either way3 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.
I am committing code that posts 10 new insights to discussion thread #424, but this commit does not resolve discussion #424. Should the commit include Addresses-Discussion: #424 in its footer?
| Checked | Without skill | With skill |
|---|---|---|
| Omits the Addresses-Discussion: trailer line when the commit does not resolve the finding. | Missed | Passed |
The instructions your model reads when the skill loads.
Gather context (run in parallel):
git status -sbgit diff --cached --statgit diff --cachedgit log --oneline -5leyline:sem-integration):
sem diff --staged --json for entity-level changesIf nothing is staged, tell the user and stop.
When sem output is available, use entity names (function, class, method) in the commit subject and body instead of parsing raw diff hunks. For example, "add function validate_webhook_url" instead of "add validation logic to notify.py".
Classify: Pick type (feat, fix, docs, refactor,
test, chore, style, perf, ci) and optional scope.
Draft the message:
<type>(<scope>): <imperative summary> (50 chars max)3a. Discussion trailer: when the change resolves a finding from the Discussions board, add a trailer on its own line:
test cases passed, vs 13 / 18 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.