Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit.
Passed 11 of 18 test cases with the skill, and 7 of 18 without it.
and 2 more in the full report
5 fixed8 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I finished committing `src/helpers/date.ts` with hash `a1b2c3d`. What final prompt step must be presented to the developer after the commit succeeds?
| Checked | Without skill | With skill |
|---|---|---|
| Prompts the developer to document any learnings or insights after committing. | Missed | Passed |
The instructions your model reads when the skill loads.
Use when saying "commit", "save changes", or ready to commit after making changes.
git status
git diff --stat
npm run lint 2>&1 | tail -5
npm run typecheck 2>&1 | tail -5
npm test -- --changed --passWithNoTests 2>&1 | tail -10
git add <specific files>
git commit -m "<type>(<scope>): <summary>"
Before committing, check staged changes in production code (not test files) for:
console.log / debugger statements (suppressed in test files — see Review Suppressions)TODO(JIRA-123) is fine)Flag any issues before proceeding.
test cases passed, vs 7 / 18 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.