spec-driven-magic/sdx-commit
Analyzes git changes, groups them by logical change or OpenSpec feature, and creates conventional commits for each group.
91
Quality
89%
Does it follow best practices?
Impact
94%
1.02xAverage score across 5 eval scenarios
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 actions, uses natural developer terminology, explicitly states both capabilities and trigger conditions, and carves out a distinct niche around commit organization and grouping rather than just generic git operations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyzes git changes', 'groups them by logical change or OpenSpec feature', and 'creates conventional commits for each group'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (analyzes git changes, groups by logical change/feature, creates conventional commits) AND when ('Use when organizing staged changes, splitting commits into atomic units, or creating structured commits instead of one mixed commit'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'staged changes', 'splitting commits', 'atomic units', 'structured commits', 'conventional commits', 'git changes'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on commit organization and grouping. The specific mention of 'OpenSpec feature', 'atomic units', and 'conventional commits' distinguishes it from generic git or commit message skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent workflow clarity and concrete executable commands. The main weakness is moderate verbosity—it explains some concepts Claude already knows (conventional commit basics) and has some redundancy between sections. The content could be tightened by ~20-30% without losing clarity.
Suggestions
Remove or condense the commit message format rules that Claude already knows (e.g., 72-char limit, conventional commit types) to just the project-specific conventions
Consolidate the Guidelines section into the Steps where relevant, eliminating repetition about conciseness and grouping
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., explaining conventional commit format that Claude knows, listing obvious rules like '≤ 72 characters'). The guidelines section repeats concepts already covered in the steps. | 2 / 3 |
Actionability | Provides fully executable bash commands at each step, concrete examples of commit message formats, and specific grouping priorities. The workflow is copy-paste ready with clear command sequences. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (1-6), explicit validation checkpoints (review staged summary before commit, confirm all commits at end), and a confirmation gate before staging/committing. Handles edge cases like mixed files. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (Steps, Commit Message Format, Guidelines), but the skill is somewhat long (~100 lines) and could benefit from separating the commit message format reference into a linked file. No external references are provided. | 2 / 3 |
Total | 10 / 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.
Install with Tessl CLI
npx tessl i spec-driven-magic/sdx-commit@0.1.1Reviewed
Table of Contents