This skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.
91
53%
Does it follow best practices?
Impact
98%
1.04xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/devops/git-commit-smart/skills/git-commit-smart/SKILL.mdBreaking change detection
Conventional format
100%
100%
Correct type
100%
100%
Scope present
100%
100%
Breaking change marker
100%
100%
Breaking change explanation
100%
100%
Describes the rename
100%
100%
Message output file
100%
100%
Imperative mood
100%
100%
Commit type inference
Conventional format
100%
100%
Type is fix
100%
100%
Scope present
100%
100%
Crash/null reference described
100%
100%
No breaking change marker
100%
100%
Subject under 72 chars
100%
100%
Message output file
100%
100%
User context incorporation
Conventional format
100%
100%
Type is fix
100%
100%
Scope present
100%
100%
Security mention in message
100%
100%
Parameterization described
100%
100%
No f-string/interpolation praised
100%
100%
No breaking change marker
100%
100%
Message output file
100%
100%
Refactor commit type selection
Type is refactor
100%
100%
Conventional format
100%
100%
Scope present
0%
100%
No breaking change marker
100%
100%
Imperative mood
100%
100%
Describes deduplication
100%
100%
Body present
100%
100%
Message output file
100%
100%
Documentation commit type selection
Type is docs
100%
100%
Conventional format
100%
100%
Scope present
0%
0%
No breaking change marker
100%
100%
Imperative mood
100%
100%
Covers JSDoc addition
100%
100%
Covers README update
100%
100%
Message output file
100%
100%
Performance commit type selection
Type is perf
100%
100%
Conventional format
100%
100%
Scope present
0%
100%
No breaking change marker
100%
100%
Imperative mood
100%
100%
Caching mechanism described
100%
100%
Performance impact mentioned
100%
100%
Message output file
100%
100%
feat commit type selection
Type is feat
100%
100%
Conventional format
100%
100%
Scope present
100%
100%
No breaking change marker
100%
100%
Imperative mood
100%
100%
Describes notification preferences
100%
100%
Body or multi-component description
100%
100%
Message output file
100%
100%
test commit type selection
Type is test
100%
100%
Conventional format
100%
100%
Scope present
100%
100%
No breaking change marker
100%
100%
Imperative mood
100%
100%
References payment or currency testing
100%
100%
Mentions test scope breadth
100%
100%
Message output file
100%
100%
chore commit type selection
Type is chore
100%
100%
Conventional format
100%
100%
Scope present
0%
100%
No breaking change marker
100%
100%
Imperative mood
100%
100%
References tooling changes
100%
100%
Covers multiple changes
100%
100%
Message output file
100%
100%
9fad7ed
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.