commit

Generate git commit messages from staged changes

Quality

73%

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 a tight, actionable workflow with explicit safety checkpoints and clean structure. The main gap is that the literal `git commit` command is implied rather than shown, and no error-recovery loop is documented.

Suggestions

Show the actual commit invocation, e.g. `git commit -m "<type>: <description>"`, so the final step is copy-paste ready.

Add a brief feedback loop for the secret/confirmation checks (e.g. what to do if the user declines or a secret is detected).

Clarify how to handle a repo with no staged changes (e.g. prompt to stage files first) to close a workflow edge case.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a short numbered workflow plus a compact format template, with no padding or explanation of concepts Claude already knows. It clearly matches the 'every token earns its place' anchor.	5 / 5
Actionability	Concrete, runnable commands are given (`git status`, `git diff --cached`, `git log --oneline -5`, `git add <specific files>`) plus a format template. It is not 5 because the actual `git commit` invocation is never shown explicitly, leaving a minor gap.	4 / 5
Workflow Clarity	A clear numbered sequence includes safety checkpoints (secret-file warning in step 5 and user confirmation in step 6), so it is not capped at 3. It is not 5 because there is no explicit error-recovery feedback loop (validate -> fix -> retry).	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clear sections (workflow + format), which qualifies for 5 under the simple-skill exception. No bundle files exist to verify, and none are needed.	5 / 5
	Total	18 / 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 is concise and names a concrete, distinct capability, but it omits any 'Use when...' trigger guidance and only lists a single action. Adding an explicit trigger clause would lift completeness and distinctiveness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to write or review a git commit message for staged changes.'

Include an extra concrete action or synonym (e.g. 'draft', 'review') to broaden trigger coverage.

Mention natural trigger phrases users say, like 'commit message' or 'what should I commit', to reduce conflict with general git skills.

Dimension	Reasoning	Score
Specificity	Names the domain (commit messages) and one concrete action (generate from staged changes), matching the '1-2 concrete actions but not comprehensive' anchor. It is below 4 because only a single action is described, and above 2 because the action is concrete rather than generic.	3 / 5
Completeness	There is a clear 'what' (generate commit messages from staged changes) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the guidelines. It is above 2 because the 'what' is specific rather than vague.	3 / 5
Trigger Term Quality	Natural terms a user would say appear ('commit messages', 'git commit', 'staged changes'), giving good keyword coverage. It is not 5 because no synonyms or extensions (e.g. 'commit message', 'uncommitted', 'patch') are included.	4 / 5
Distinctiveness Conflict Risk	The git-commit niche is mostly distinct with only minor overlap risk against general git skills. It is not 5 because the absence of explicit trigger phrases keeps it from a fully distinct, minimal-conflict profile.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/commit/SKILL.md
Commit: 94b7187

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