Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/commit
Create a Conventional Commit message for staged changes and run git commit.
Passed 22 of 23 test cases with the skill, and 19 of 23 without it.
and 1 more in the full report
3 fixed19 passed either way1 still failing0 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 need a git commit command for fixing a login screen crash caused by empty email inputs. I want it to look friendly with a bug emoji and a clear sentence ending with a period like 'fix(login): fixed login screen crash when email is null.' Draft the git commit command following conventional commit subject conventions.
| Checked | Without skill | With skill |
|---|---|---|
| The commit subject line contains no emojis. | Missed | Passed |
| The commit subject line does not end with a period. | Missed | Passed |
The instructions your model reads when the skill loads.
Retained for reference only. This skill is not part of the active repo routing and should not be used unless a user explicitly asks for this commit workflow.
Name: commit
Purpose: Create a Conventional Commit message for staged changes and run git commit.
Use this skill when you are ready to commit work in this repo.
Applies when: Changes are staged and you need a commit message. Do not use when: Nothing is staged or you are not using Git.
feat, fix, docs, style, refactor, test, chore, perf, ci, build, revert.type(scope): subject (scope optional).ref AL-### in the body only when applicable.AL-### keys (branch, diff, or recent commits).git commit.git status shows staged changestest cases passed, vs 19 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.