commit

Read this skill before making git commits

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 ./skills/commit/SKILL.md

Quality

Content

86%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 lean, well-structured, and actionable, with concrete git commands, a precise Conventional Commits format spec, and a sensible workflow that includes a user-clarification checkpoint. Its only gaps are a missing worked commit-message example and a post-commit verification step.

Dimension	Reasoning	Score
Conciseness	Terse bullets and a format template assume Claude's knowledge of git and Conventional Commits with no padding or concept re-explanation; every line is actionable guidance and every token earns its place.	5 / 5
Actionability	Concrete executable commands (git status, git diff, git log -n 50 --pretty=format:%s, git commit -m) and a format spec are provided, but no worked example of a complete commit message is shown, leaving a minor gap versus fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	A clear 6-step sequence includes a clarification checkpoint (step 4: ask the user about ambiguous files); committing is non-destructive and non-batch so the cap-3 rule does not apply, though a post-commit verification step is absent.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, requires no external references, and is organized into well-signaled sections (Format, Notes, Steps), satisfying the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

40%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 a meta-instruction ('Read this skill before making git commits') rather than a capability statement: it conveys the niche but not what the skill does or explicit trigger phrases. It is distinct and uses one natural keyword, but lacks the 'what' and an explicit 'when' clause.

Suggestions

Rewrite as a capability + trigger statement, e.g. 'Create git commits with a concise Conventional Commits-style subject. Use when the user asks to commit changes, write a commit message, or stage and commit files.'

State the concrete action ('Create git commits … Conventional Commits-style subject') instead of the meta 'Read this skill before …'.

Add natural trigger synonyms such as 'commit message', 'commit my changes', or 'stage and commit' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('making git commits') but the only stated action is the meta-instruction 'Read this skill'; no concrete capability such as drafting Conventional Commits messages is described, placing it below the midpoint between anchors 1 and 3.	2 / 5
Completeness	A weak 'when' ('before making git commits') is present, but the 'what' is absent—replaced by the meta 'read this skill'—so it matches the anchor 'only when present without what', and the missing explicit 'Use when...' guidance caps completeness below 3.	2 / 5
Trigger Term Quality	'git commits' is a specific, natural term users actually say rather than generic jargon, but only one keyword phrase appears and variations like 'commit message' are missing, fitting anchor 3 over anchor 2.	3 / 5
Distinctiveness Conflict Risk	'git commits' is a clear, distinct niche unlikely to trigger the wrong skill; phrasing is meta rather than a natural trigger, leaving minor overlap risk with closely related git skills.	4 / 5
	Total	11 / 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: mitsuhiko/agent-stuff
Path: skills/commit/SKILL.md
Commit: 13bc8f8

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