Stage and commit changes following conventional commits. Auto-bumps package versions before committing.
84
80%
Does it follow best practices?
Impact
90%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/commit/SKILL.mdVersion bump and full commit workflow
bump-versions executed
100%
100%
package.json versions bumped
100%
100%
package.json files staged
100%
100%
typecheck executed
100%
100%
Conventional commit type
100%
100%
Lowercase description
100%
100%
No trailing period
100%
100%
Under 72 chars
100%
100%
Co-Authored-By trailer
0%
0%
Selective staging
100%
100%
Post-commit git status
0%
100%
build:core reminder
0%
100%
Publish workflow reminder
100%
100%
Commit message format and safety guardrails
Allowed commit type
100%
100%
Lowercase description
100%
100%
No trailing period on subject
100%
100%
Subject line length
100%
0%
Co-Authored-By trailer
0%
50%
Why-focused message
100%
100%
No push performed
100%
100%
No amend used
100%
100%
No --no-verify used
100%
100%
git status after commit
100%
100%
Scope included
100%
100%
Selective staging with security awareness
.env excluded
100%
100%
Unrelated changes excluded
100%
100%
Specific git add used
100%
100%
bump-versions executed
50%
80%
package.json staged
100%
100%
typecheck executed
50%
80%
Conventional commit type
100%
100%
Co-Authored-By trailer
0%
100%
Lowercase, no period
100%
100%
No push performed
100%
100%
1a11b95
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.