Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/commit
Read this skill before making git commits
3 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Generate a commit command for my updates to the `v2/auth` endpoint. Note that this introduces a breaking change by dropping compatibility with old clients since the payload signature changed. Make sure that breaking change context is documented in the standard structure.
| Checked | Without skill | With skill |
|---|---|---|
| Excludes the exclamation mark character (`!`) from the commit type prefix. | Missed | Passed |
| Excludes a 'BREAKING CHANGE' footer from the message. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a git commit for the current changes using a concise Conventional Commits-style subject.
<type>(<scope>): <summary>
type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.Signed-off-by).git status and git diff to understand the current changes (limit to argument-specified files if provided).git log -n 50 --pretty=format:%s to see commonly used scopes.git commit -m "<subject>" (and -m "<body>" if needed).test cases passed with the skill
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.