Optionally checks, then commits code to the current or a new feature branch.
68
52%
Does it follow best practices?
Impact
94%
1.30xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/commit/SKILL.mdFeature branch creation and conventional commit format
git status invoked
0%
0%
git diff HEAD invoked
0%
0%
git log consulted
0%
100%
Feature branch created
0%
100%
Conventional format: type
0%
100%
Conventional format: scope
0%
100%
Message length ≤ 72 chars
100%
100%
Files staged with git add
100%
100%
Commit hash reported
100%
100%
Commit message reported
100%
100%
Pre-commit check mode enforcement and stopping on failure
git status invoked
60%
100%
git diff HEAD invoked
0%
80%
git log consulted
0%
100%
Tests executed
100%
100%
Check failure detected
100%
100%
No commit created
100%
100%
Failure reason documented
100%
100%
Conventional format (if commit)
0%
0%
Force mode, secret file exclusion, plain-string commit message
.env not committed
100%
100%
No other secret files
100%
100%
Checks skipped (force mode)
100%
100%
No HEREDOC in commit command
100%
100%
Conventional format: type
100%
100%
Message length ≤ 72 chars
100%
100%
Commit hash reported
100%
100%
Commit message reported
100%
100%
d93dc41
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.