commit
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
83
87%
Does it follow best practices?
Impact
56%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
57%
9%Commit a Feature Branch Change
Commit message format and structure
Conventional type prefix
0%
100%
Imperative subject
100%
100%
Subject line length
100%
100%
No trailing period on subject
100%
100%
Summary section present
0%
0%
Rationale section present
0%
0%
Tests section present
0%
0%
Co-authored-by trailer
0%
0%
Body line wrapping
100%
100%
Used git commit -F
100%
100%
Blank line after subject
100%
100%
60%
Commit a Bug Fix with a Cluttered Working Directory
Selective staging with cluttered working tree
Excludes build artifacts
100%
100%
Excludes temp/log files
100%
100%
Excludes unrelated changes
100%
100%
Includes the bug fix
100%
100%
Staging notes written
100%
100%
Conventional type prefix
100%
100%
Imperative subject
100%
100%
Summary section
0%
0%
Rationale section
0%
0%
Tests section
0%
0%
Co-authored-by trailer
0%
0%
56%
-8%Finalize a Refactoring Commit with Full Context
Session history integration in commit rationale
Rationale from session
100%
100%
Trade-off mentioned
100%
100%
Tests section with command
100%
60%
Summary section present
0%
0%
Rationale section present
0%
0%
Tests section present
0%
0%
Conventional type prefix
100%
100%
Imperative subject
100%
100%
Co-authored-by trailer
0%
0%
Used git commit -F
100%
100%
Body line wrapping
100%
50%
- Repository
- openai/symphony
- Commit
4cbe3a9
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
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.