Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ccplugins/commit-craft
Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and safe to ship.
Passed 13 of 18 test cases with the skill, and 8 of 18 without it.
and 4 more in the full report
6 fixed10 passed either way6 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 message subject line for updating the database schema in `prisma/schema.prisma` to add a `deletedAt` timestamp field.
| Checked | Without skill | With skill |
|---|---|---|
| Omits a trailing period at the end of the commit subject line | Passed | Passed |
| Starts the subject line with an imperative verb | Missed | Passed |
The instructions your model reads when the skill loads.
Version-control history is documentation that outlives every summary. A commit is read far more often than it's written — during review, bisects, blame, and reverts months later. Sloppy history turns those into archaeology; disciplined history makes them a one-line answer.
Core principle: every commit should be a single, reversible, explainable unit of change.
Any time work reaches git: staging a commit, cutting a branch, or opening a PR. Skip it only for throwaway experiments you never intend to keep. It does not depend on any other plugin being installed.
main/
master and the user hasn't said otherwise, branch first (see naming below), then commit.--no-verify, --no-gpg-sign, or skip hooks unless the user explicitly asks. A
failing hook is a signal to fix, not to bypass.Atomic. One logical change per commit. Don't mix a refactor with a feature, or a formatting
sweep with a bug fix — a reviewer (and a future git revert) should be able to take or drop the
change as a whole. Split unrelated work into separate commits.
Message format:
<imperative subject, ~50 chars, no trailing period>
<body: wrap ~72 chars. Explain WHY the change is needed and what it
affects — the diff already shows what changed. Reference issues/PRs.>
Co-Authored-By: Claude Opus 4.8 <[email protected]>
test cases passed, vs 8 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.