commitlint
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
60
Quality
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/commitlint/skills/commitlint/SKILL.mdQuality
Discovery
37%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 description is structurally inverted - it provides only 'Use when...' triggers without any 'what it does' content. While the trigger terms are specific and relevant to commitlint workflows, the complete absence of capability descriptions makes it impossible for Claude to understand what actions this skill enables.
Suggestions
Add capability statements at the beginning describing concrete actions (e.g., 'Configures and validates commit message formats using commitlint. Parses commitlint configuration files, generates conventional commit templates, and diagnoses validation errors.')
Restructure to lead with 'what' before 'when' - the current format is backwards from the expected pattern
Convert the 'when' clauses into a proper 'Use when...' sentence that follows the capability description
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only lists 'when' scenarios without describing any concrete actions or capabilities. There are no verbs describing what the skill actually does (e.g., 'validates', 'configures', 'extracts'). | 1 / 3 |
Completeness | The description only answers 'when' but completely omits 'what'. There is no explanation of what capabilities or actions this skill provides - it's entirely composed of trigger conditions without describing functionality. | 1 / 3 |
Trigger Term Quality | Contains strong natural keywords users would say: 'commitlint', 'commit message validation', 'commitlint.config.js', '.commitlintrc', 'CI/CD', 'commit format', 'commit message rejection errors'. Good coverage of technical terms and file names. | 3 / 3 |
Distinctiveness Conflict Risk | The commitlint-specific terms like 'commitlint.config.js' and '.commitlintrc' provide some distinctiveness, but without clear capability statements, it could overlap with general git/commit skills or CI/CD configuration skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive commitlint reference with excellent actionability through executable code examples and CLI commands. However, it suffers from verbosity with extensive inline tables and configuration examples that could be better organized into separate reference files. The workflow guidance for LLM integration is present but could be more explicit with validation checkpoints.
Suggestions
Move the extensive rule reference tables to a separate RULES_REFERENCE.md file and link to it from the main skill
Condense the 'When to Use This Skill' section since it largely duplicates the skill description
Transform the LLM validation loop pattern from abstract description into explicit numbered steps with validation checkpoints and error handling examples
Remove the exhaustive list of 15 config file formats and replace with 'Supports standard cosmiconfig patterns (.commitlintrc.*, commitlint.config.*)'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant information like listing all 15 config file formats and extensive rule tables that could be condensed. The 'When to Use This Skill' section repeats information already in the description. | 2 / 3 |
Actionability | Provides fully executable code examples in multiple languages (JavaScript, TypeScript, Python, bash), copy-paste ready CLI commands, and concrete configuration snippets with clear expected outcomes. | 3 / 3 |
Workflow Clarity | The LLM Integration section describes a validation loop pattern but lacks explicit step-by-step sequencing with validation checkpoints. The 5-step pattern is described abstractly rather than as executable workflow with error recovery. | 2 / 3 |
Progressive Disclosure | References to other skills (pre-commit, conventional-commits) are well-signaled, but the document is monolithic with extensive inline content (rule tables, configuration schemas) that could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (522 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Jamie-BitFlight/claude_skills
- Commit
fd243f9
- 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.