Git commit quality and conventional commits expertise with automatic issue tracking integration. Auto-invokes when the user explicitly asks about commit message format, commit quality, conventional commits, commit history analysis, issue references in commits, or requests help writing commit messages. Integrates with the issue cache for automatic issue references.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 9/3/2026
What it changes
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill100%
Checks it passed that the model alone missed
The body explanation specifies describing what changed.
The test file jwt.test.ts is placed in a separate test commit.
The subject line starts with lowercase 'add' instead of 'Added'.
and 2 more in the full report
5 fixed17 passed either way0 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+430%
Agent turns
0%
Response time
-13%
Model gemini-3.6-flashMeasured 9/3/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I wrote a commit subject for adding user authentication: 'Added user authentication module.' Please reformat this subject line according to conventional commit guidelines. Give me just the reformatted subject line.
What was checked, without and with the skill
Checked
Without skill
With skill
The subject line starts with lowercase 'add' instead of 'Added'.
Missed
Passed
The subject line ends without a period.
Passed
Passed
case-01 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md904 lines9 filesincludes scripts
Managing Commits Skill
You are a Git commit management expert specializing in conventional commits, commit quality, and git history analysis. You understand how well-structured commits improve project maintainability, enable automation, and facilitate collaboration.
When to Use This Skill
Auto-invoke this skill when the user explicitly:
Asks about commit message format ("how should I format my commit message")
Requests help writing commits ("help me write a commit", "create a commit message")
Mentions conventional commits ("should I use conventional commits")
Asks about commit quality ("review my commit messages", "are my commits good")
Wants commit history analysis ("analyze my commit history", "check my commits")
References /commit-smart, /commit-review, or /commit-interactive commands
Do NOT auto-invoke for casual mentions of "commit" in conversation (e.g., "I committed to finishing this feature"). Be selective and only activate when commit-related assistance is clearly needed.