CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit-message

Guide for writing clear, consistent git commit messages following this repository's conventions

Quality

72%

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 ./.opencode/skills/commit-message/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, actionable instruction skill that assumes Claude's competence and avoids explaining basic concepts. Its only real weaknesses are mild example redundancy and the absence of a self-check/verification checkpoint.

Suggestions

Consolidate the three overlapping example lists (legacy history, 'better current-style', Quick Template) into one canonical set to tighten conciseness.

Add a short 'Self-check' checkpoint (imperative mood, no trailing period, <=72 chars, correct type from decision tree) to strengthen workflow clarity.

Consider moving the legacy-history example block into a clearly labeled 'Deprecated/old repo style' subsection so time-sensitive style drift is isolated.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude knows git/commits, but the repeated example inventories (legacy history, 'better current-style', and Quick Template) are mild redundancy that could be trimmed, fitting the 'efficient; minor over-explanation' anchor rather than the fully lean 5.

4 / 5

Actionability

Concrete, specific guidance throughout—an explicit format, a types table with real examples, a decision tree, and a fill-in template—covers the common cases well; for an instruction-only skill this is just shy of fully copy-paste ready, hence above 4 but not quite 5.

4.5 / 5

Workflow Clarity

The decision tree gives a clear sequenced flow for choosing a type and the rules are numbered, but there is no self-verification checkpoint (e.g., re-check imperative mood or 72-char limit), keeping it just below 5.

4 / 5

Progressive Disclosure

No bundle files exist and the body is cleanly organized into well-signaled sections (Purpose, Format, Types, Rules, Decision Tree, Examples, Quick Template) with no nested or buried references, meeting the simple-skill bar for a 5.

5 / 5

Total

17.5

/

20

Passed

Description

51%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 concise and third-person with a clear purpose, but it omits any explicit 'Use when...' trigger guidance and lists few concrete actions. Adding trigger phrases and one or two specific capabilities would lift the completeness and specificity scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing or reviewing git commit messages, or when the user asks for a commit message.'

Name a couple of concrete actions (e.g., 'choose a Conventional Commits type, format the subject, add a body and Co-authored-by trailers') to move specificity above 3.

Include natural synonyms like 'commits' or 'git log' alongside 'commit messages' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('git commit messages') but the action is generic ('Guide for writing... clear, consistent'), offering no enumerated concrete actions, placing it between the 'minimal actions' (2) and '1-2 concrete actions' (3) anchors.

2.5 / 5

Completeness

It gives a clear 'what' (a guide for writing commit messages per repo conventions) but no 'when'/'Use when' trigger clause, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

'git commit messages' is a relevant natural keyword, but the description lacks common synonyms (commits, git log) and any explicit trigger phrase, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Commit-message authoring tied to 'this repository's conventions' is a distinct niche with minor overlap risk, but without explicit trigger phrases it falls short of the 5 anchor.

4 / 5

Total

12.5

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

EvolvingLMMs-Lab/LLaVA-OneVision-2

Path

.opencode/skills/commit-message/SKILL.md

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.