commit-work
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
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, uses natural trigger terms users would actually say, explicitly addresses both what and when, and carves out a distinct niche around git commit workflows. The description follows proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits)'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages') AND when ('Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'commit', 'commit message', 'stage changes', 'split work into multiple commits'. These match common user vocabulary when working with git. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on git commits with distinct triggers like 'commit', 'stage changes', 'Conventional Commits'. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It provides a clear, actionable workflow with explicit validation checkpoints and feedback loops for error recovery. The content is concise, assumes Claude's competence with git, and appropriately references external resources for detailed templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and concise commands without explaining basic git concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides specific, executable git commands throughout (git add -p, git diff --cached, git restore --staged -p). The workflow is concrete with copy-paste ready commands and clear decision criteria for splitting commits. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with numbered checklist, explicit validation checkpoints (step 4 sanity checks, step 5 description test, step 7 verification), and a clear feedback loop (go back to step 2 if commit is too big). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Goal, Inputs, Workflow, Deliverable). References external file (commit-message-template.md) appropriately for detailed template content. Content is appropriately scoped for a SKILL.md overview. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- softaworks/agent-toolkit
- Commit
3027f20
- Reviewed
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.