CtrlK
BlogDocsLog inGet started
Tessl Logo

git-commit-messages

Write clear, conventional commit messages that explain the why behind changes.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./git-commit-messages/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a lean, well-structured single-purpose skill with concrete, actionable guidance and clear organization. It earns top marks on conciseness, workflow clarity, and progressive disclosure, with only minor actionability gaps around broader case coverage.

DimensionReasoningScore

Conciseness

Lean and tight: a format template, a short type list, four concise guideline bullets, and two brief examples, with no padding or explanation of concepts Claude already knows, matching anchor 5.

5 / 5

Actionability

Provides a concrete format template, a usable type list, actionable rules (imperative mood, under 72 chars, no period), and a copy-paste-ready good example, but lacks coverage of several common cases or an actual git commit command, matching anchor 4.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines where the single action (write a conventional commit message) is unambiguous and the guidelines act as a clear checklist, qualifying for the simple-skill exception at anchor 5.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized into Format / Guidelines / Examples with no need for external references, fitting the guideline that simple skills can score 5 with well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

53%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 is clear and specific about what the skill does but omits any explicit 'when to use it' trigger guidance, which caps its completeness. Trigger-term coverage is adequate but lacks common synonyms. It is reasonably distinct from other skills.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases such as 'writing a commit message', 'reviewing staged changes', or 'git commit'.

Broaden trigger terms with synonyms users naturally say (e.g. 'git commit', 'staged changes', 'commit message') to improve trigger_term_quality.

Expand the 'what' with one or two more concrete actions (e.g. amending, scoping) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('conventional commit messages') with one to two concrete actions ('Write clear... commit messages', 'explain the why'), but coverage is not comprehensive, matching anchor 3.

3 / 5

Completeness

Has a clear 'what' (write conventional commit messages explaining the why) but no explicit 'Use when...' trigger clause, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Includes the natural phrase 'commit messages' but misses common variations users say such as 'git commit' or 'staged changes', fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

'Conventional commit messages' is a mostly distinct niche with minor overlap risk versus general git or writing skills, matching anchor 4.

4 / 5

Total

13

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
neil-tessl/nh-code-review-skills
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.