git-commit-messages

When you need to write git commit messages, follow conventional commits format with clear descriptions.

Quality

83%

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

Quality

Content

92%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.

A tight, well-structured, highly actionable reference for writing conventional commit messages that respects Claude's competence and needs no bundle files. The only nit is minor redundancy between the Rules and Scope Guidelines sections.

Dimension	Reasoning	Score
Conciseness	The body is lean reference material with no over-explanation of concepts Claude already knows, though Rules and Scope Guidelines overlap slightly on scope guidance and could be consolidated.	4 / 5
Actionability	Provides a concrete format template, a type list, specific rules (under 72 chars, imperative mood), and two copy-paste-ready examples covering the common feat/fix cases.	5 / 5
Workflow Clarity	A simple single-purpose skill whose single action (write a conventional commit message) is unambiguous, and the content is clearly organized into format, types, rules, examples, and scope.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references, and content is well-organized into clearly labeled sections, satisfying the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

73%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.

A concise, distinct description that answers both what and when with a natural trigger phrase. It would benefit from listing a couple more concrete capabilities and trigger variations.

Suggestions

Add one or two more concrete actions (e.g., 'analyze staged diffs to generate commit messages') to lift specificity.

Include additional natural trigger phrases such as 'committing changes' or 'reviewing staged changes' to broaden trigger coverage.

Make the 'when' clause slightly more explicit by naming scenarios beyond just writing, such as amending or splitting commits.

Dimension	Reasoning	Score
Specificity	Names the domain ('git commit messages') and the method ('follow conventional commits format') but lists only one concrete action rather than multiple specific capabilities.	3 / 5
Completeness	Both 'what' (follow conventional commits format with clear descriptions) and an explicit 'when' (When you need to write git commit messages) are present, but the trigger scenario is singular and could be more specific.	4 / 5
Trigger Term Quality	'write git commit messages' is a natural phrase users would say, giving good keyword coverage, though synonyms like 'commit', 'committing', or 'reviewing staged changes' are absent.	4 / 5
Distinctiveness Conflict Risk	Git commit messages form a clear niche with a distinct, unambiguous trigger and minimal overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: neil-tessl/skill-index-evals-dev
Path: git-commit-messages/SKILL.md
Commit: 2bad92e

Reviewed: 10 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.