Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/clean-commits
Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
1 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I'm about to submit a pull request, but my local branch has about eight messy commits including quick WIP saves, typo fixes, and refactoring mixed with the main feature. How should I clean up this commit branch before requesting a code review?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using `git rebase -i` to squash preliminary commits | Passed | Passed |
| Instructs keeping refactoring and feature changes in separate commits | Passed | Passed |
| Specifies using imperative mood for the commit subject | Missed | Passed |
The instructions your model reads when the skill loads.
git rebase -i).git bisect and git blame only work if commits are atomic and messages explain intent.test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.