commit
Pre-commit review gate, semantic commit format, and squashing guidance
78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (git commits and pre-commit workflows) but lacks the explicit trigger guidance and concrete action verbs needed for reliable skill selection. It reads more like a feature list than actionable guidance for when Claude should select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about commit messages, pre-commit hooks, squashing commits, or conventional commit format'
Replace abstract nouns with concrete verbs: 'Validates staged changes before commit, formats commit messages using conventional commit syntax, guides squashing multiple commits'
Include natural user terms: 'git commit', 'commit message', 'staged changes', 'merge commits', 'rebase'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (commit-related) and some actions (review gate, semantic format, squashing guidance), but these are somewhat abstract rather than concrete actions like 'generate commit messages' or 'validate commit format'. | 2 / 3 |
Completeness | Only describes 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing entirely the 'when should Claude use it' component, which per rubric caps this at maximum 2, but the 'what' is also weak. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'commit', 'squashing', and 'pre-commit', but missing common user terms like 'git', 'commit message', 'staged changes', or file extensions. Users might say 'help me write a commit' which wouldn't clearly match. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to git commits and pre-commit workflows, but 'semantic commit format' could overlap with general code style or linting skills. The niche is identifiable but not sharply defined. | 2 / 3 |
Total | 7 / 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 strong technical writing. It's concise yet comprehensive, with clear workflows, concrete examples, and well-organized sections. The pre-commit validation loop and the nuanced guidance on squashing (before vs after push) show thoughtful workflow design.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanations of concepts Claude already knows (like what commits are or how git works). Tables and examples are compact and information-dense. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready examples for commit messages, branch renaming commands, and PR descriptions. The format specifications are explicit and immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow in 'Before Every Commit' with explicit validation checkpoint (/review staged with repeat-until-no-blockers loop). Squashing section clearly distinguishes before-push vs after-review behavior. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers. Content is appropriately scoped for a single SKILL.md file—no need for external references given the focused topic. Easy to navigate and find specific guidance. | 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.
- 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.