Install any skill in seconds. Free to start, no credit card required.
Get Started Free →elianiva/commit
Conventional commit message generator for jj and git repos. Analyzes diffs and produces scoped, well-formed commit messages.
Passed 18 of 22 test cases with the skill, and 18 of 22 without it.
1 fixed20 passed either way3 still failing1 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 am ready to save my progress in a project directory. Should I run git status or check if Jujutsu is available first?
| Checked | Without skill | With skill |
|---|---|---|
| Prioritizes checking for Jujutsu over Git. | Passed | Passed |
| Uses the detection command checking jj root. | Missed | Passed |
The instructions your model reads when the skill loads.
Commit based on previous conversation if there's any, otherwise check the diff.
# returns "jj" or "git"
which jj 2>/dev/null && jj root 2>/dev/null && echo "jj" || (git rev-parse --show-toplevel 2>/dev/null && echo "git")
Prefer jj if both work — it's the user's primary VCS.
jj status # changed files
jj diff # full diff
jj diff <file> # specific file
jj describe -m "<type>(<scope>): <subject>"
With body:
jj describe -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body>
EOF
)"
test cases passed, vs 18 / 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.