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.

Quality

39%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/commitlint/skills/commitlint/SKILL.md

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a mirror of commitlint's official documentation crammed into a single file. While it excels at actionability with executable code examples across multiple languages, it is far too verbose—the exhaustive rule reference tables, configuration file listings, and case value enumerations waste significant token budget on information Claude can access or infer. The content would benefit enormously from splitting reference material into separate files and keeping only the essential workflow and integration patterns in the main SKILL.md.

Suggestions

Move the exhaustive rule reference tables (Type, Subject, Scope, Header, Body, Footer rules) and case values into a separate RULES_REFERENCE.md file, keeping only the most common rules inline.

Remove the configuration detection file listing (15 filenames) and replace with a one-line note that commitlint uses cosmiconfig; Claude knows how cosmiconfig works.

Consolidate configuration format examples to just one recommended format (ESM) with a brief note about alternatives, rather than showing JS, TS, JSON, and YAML variants.

Make the LLM validation loop pattern concrete with executable code rather than an abstract numbered list of steps.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Exhaustive rule reference tables (type, subject, scope, header, body, footer rules) are documentation Claude can look up. The config detection file listing, case values reference, complete configuration schema, and exit codes table all add bulk that Claude already knows or could infer. This reads like a full documentation mirror, not a skill.	1 / 3
Actionability	Provides fully executable code examples across JavaScript, TypeScript, Python, and CLI commands. Installation commands, validation functions, and configuration examples are all copy-paste ready with concrete values.	3 / 3
Workflow Clarity	The LLM validation loop pattern outlines steps but lacks explicit validation checkpoints and error recovery details. The 'validation loop pattern' is described as a numbered list of abstract steps rather than concrete executable workflow. The pre-commit integration just points to another skill without guidance.	2 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files to offload content to. The exhaustive rule reference tables, complete configuration schema, and case values reference should be in separate reference files. Cross-references to other skills exist but the core content is not split at all.	1 / 3
	Total	7 / 12 Passed

Description

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 heavily imbalanced—it provides excellent trigger scenarios and 'when to use' guidance but completely omits what the skill actually does. The lack of any capability description (the 'what') makes it impossible for Claude to understand the skill's function, even though the trigger terms are well-chosen and specific to the commitlint domain.

Suggestions

Add a clear 'what' statement at the beginning describing concrete actions, e.g., 'Parses commitlint configuration files, validates commit message formats, and generates compliant commit message templates.'

Restructure to lead with capabilities before the 'Use when...' triggers, following the pattern: '[What it does]. Use when [trigger scenarios].'

Consolidate the five 'When...' clauses into a single 'Use when...' sentence to reduce verbosity while retaining the strong trigger terms.

Dimension	Reasoning	Score
Specificity	The description only lists 'when' scenarios but never describes concrete actions or capabilities. There are no verbs describing what the skill actually does (e.g., 'parses commitlint config', 'generates commit message templates'). The phrases like 'setting up', 'configuring', 'extracting', 'debugging' hint at domains but don't specify what the skill performs.	1 / 3
Completeness	The description answers 'when' extensively but completely fails to answer 'what does this do'. There is no explanation of the skill's capabilities or actions—only a list of trigger scenarios. The 'what' component is entirely missing.	1 / 3
Trigger Term Quality	Contains strong natural trigger terms users would actually use: 'commitlint.config.js', '.commitlintrc', 'commit message validation', 'CI/CD', 'commit format', 'commit rules', 'LLM prompt generation', 'commit message rejection errors'. These cover multiple natural variations of how users would describe commitlint-related tasks.	3 / 3
Distinctiveness Conflict Risk	The commitlint focus and specific file references (commitlint.config.js, .commitlintrc) provide some distinctiveness, but the broad mentions of 'CI/CD', 'commit message', and 'LLM prompt generation' could overlap with general git workflow or CI/CD skills. Without stating what the skill does, it's harder to distinguish from related skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: 2f639b2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.