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

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%Weight 40%Scale 1-5

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

The content is highly actionable with executable examples across config formats, CLI, and programmatic APIs, and includes a useful validation feedback loop. However, it is a large monolithic reference that would benefit from progressive disclosure into separate bundled reference files.

Suggestions

Move the exhaustive 'Rule Reference' tables and 'Complete Configuration Schema' into separate reference files (e.g. references/rules.md, references/schema.md) and link to them from SKILL.md.

Tighten verbose commented schema blocks to only the non-obvious fields to improve token efficiency.

Add a brief end-to-end 'Getting started' workflow at the top that sequences install → configure → lint → interpret exit codes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material without 'what is a commit message' padding, but at ~510 lines it includes exhaustive rule tables and a fully-commented complete schema that could be tightened or moved to reference files.	3 / 5
Actionability	It provides copy-paste ready installation commands, CLI invocations, executable JS/TS/JSON/YAML config examples, and Python snippets for programmatic validation and rule extraction covering the common cases.	5 / 5
Workflow Clarity	The LLM 'Validation loop pattern' is a clear sequenced feedback loop (generate → lint → feed errors back → retry), but the skill is otherwise reference-oriented with no end-to-end workflow tying the sections together.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but no bundle files exist and large reference blocks (full rule tables, complete schema) are inlined in SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 has strong, specific trigger guidance and is clearly distinct as a commitlint skill, but it omits an explicit 'what does this skill do' statement, relying only on 'When ...' clauses. Adding a leading declarative sentence (e.g. 'Validate commit messages against Conventional Commits format using commitlint.') would make it complete.

Suggestions

Prepend a concise declarative 'what' sentence before the 'When ...' clauses, e.g. 'Validates commit messages against Conventional Commits format using commitlint configuration and rules.'

Add a couple of natural user phrasings as triggers, such as 'lint my commit messages' or 'commitlint is rejecting my commits'.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions such as 'setting up commit message validation', 'configuring CI/CD to enforce commit format', 'extracting commit rules for LLM prompt generation', and 'debugging commit message rejection errors' — several specific actions with only minor coverage gaps.	4 / 5
Completeness	The description consists entirely of 'When ...' trigger clauses with strong, explicit 'when' guidance but no declarative 'what' statement of what the skill does, matching the anchor where only 'when' is present without an explicit 'what'.	2 / 5
Trigger Term Quality	It includes natural trigger terms users would say, including concrete config file names ('commitlint.config.js', '.commitlintrc'), 'CI/CD to enforce commit format', and 'commit message rejection errors'; a few natural synonyms (e.g. 'lint my commits') are missing.	4 / 5
Distinctiveness Conflict Risk	Commitlint-specific triggers such as 'commitlint.config.js' and '.commitlintrc' files define a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (517 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Jamie-BitFlight/claude_skills
Path: plugins/commitlint/skills/commitlint/SKILL.md
Commit: c337daf

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.