Create a well-formatted commit message from staged changes
NewMaintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 21 of 22 test cases with the skill, and 21 of 22 without it.
Without skill95%
With skill95%
0 fixed21 passed either way1 still failing0 broke
Pass-rate lift
0 pp
Tokens
-7%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/20/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md33 linessingle file
Git Commit
Purpose
Create a well-formatted commit message from staged changes
Routing
Use when: Use when the user asks to create a well-formatted commit message from staged changes.
Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
Outputs: Outcome from Git Commit: task-specific result plus concrete action notes.
Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
Use the git-commit skill for this request.
Help me with git commit.
Use when the user asks to create a well-formatted commit message from staged changes.
Git Commit: provide an actionable result.
Negative
Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
Do not use git-commit for unrelated requests.
This request is outside git commit scope.
This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
Current runtime prompt length: 494 characters.
Runtime prompt is defined directly in ../git-commit.json.