Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
99
100%
Does it follow best practices?
Impact
95%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Splitting mixed changes into logical commits
Multiple commits
100%
100%
Conventional Commits type
100%
100%
Conventional Commits structure
100%
100%
Imperative summary
100%
100%
Body content: what/why
100%
100%
Logical split: bug fix separate
100%
100%
Logical split: feature separate
100%
100%
git diff --cached in report
0%
100%
Staging commands documented
100%
100%
Per-commit summary
100%
100%
git log included
100%
100%
Conventional Commits message quality
Conventional Commits subject
100%
100%
Blank line separator
100%
100%
Imperative summary verb
100%
100%
Body explains why
100%
100%
Body avoids implementation detail
60%
70%
git diff --cached reviewed
100%
100%
Sanity check noted
100%
100%
Lint/check run
100%
100%
Per-commit what/why summary
100%
100%
Full commit message in report
100%
100%
Breaking change commit notation
Breaking change marker in header
100%
100%
BREAKING CHANGE footer
100%
100%
Conventional Commits subject
30%
70%
Imperative summary
100%
100%
Body: behavior and intent
100%
100%
Migration instruction
100%
100%
git diff --cached reviewed
100%
100%
Staging commands documented
100%
100%
Sanity check: no secrets
0%
0%
Full commit message in report
100%
100%
3027f20
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.