Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vstorm-co/git-workflow
Git operations: commits, branches, PRs, and conflict resolution
Passed 21 of 22 test cases with the skill, and 12 of 22 without it.
and 7 more in the full report
9 fixed12 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just fixed a memory leak in the data parser. I'm tempted to use `bugfix: fix memory leak` or `fix(parser): fix memory leak`. What exact commit header line should I write?
| Checked | Without skill | With skill |
|---|---|---|
| Uses type prefix fix: without scope parentheses | Missed | Passed |
| Description begins with a lowercase verb | Passed | Passed |
The instructions your model reads when the skill loads.
Format: <type>: <description>
Types: feat, fix, refactor, test, docs, style, chore
git checkout -b feat/descriptiongit fetch origingit rebase origin/main (or merge if team prefers)git rebase --continuegit diff before committinggit stash before switching branches with uncommitted changestest cases passed, vs 12 / 22 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.