Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 20% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 1% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 213% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 39% | 0% |
Use when saying "commit", "save changes", or ready to commit after making changes.
bashgit 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.
<type>(<scope>): <short summary>
<body - what changed and why>Types: feat, fix, refactor, test, docs, chore, perf, ci, style
git add -A or git add ..Do NOT flag these during the pre-commit scan. They add noise without catching real bugs:
console.log in test filesOther measured skills in the registry, with their headline benchmark lift.