commit

Stage changes and write a clean Conventional-Commit message that follows the repo's git rules

Quality

77%

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

Quality

Content

93%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, executable four-step commit workflow with concrete commands and a validation checkpoint, well-structured for a simple skill.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — direct commands with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready commands (git status/diff/add/commit heredoc/log) with a concrete example commit message covering the common case.	5 / 5
Workflow Clarity	Clear four-step sequence (Inspect, Compose, Commit, Confirm) with an explicit verification checkpoint in step 4, but no explicit error-recovery feedback loop if verification fails.	4 / 5
Progressive Disclosure	Well-organized sections under 50 lines with no need for external references; the single one-level reference to .agents/rules/git-github.md is clearly signaled and appropriate.	5 / 5
	Total	19 / 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 specific about the what, but omits explicit trigger guidance for when to invoke the skill, which limits its completeness score.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when the user asks to commit, stage, or write a Conventional-Commit message').

Include a natural synonym such as 'git commit' or 'commit message' to broaden trigger coverage.

Optionally name a third concrete action (e.g. reviewing the staged diff) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (commit messages) and two concrete actions — 'Stage changes' and 'write a clean Conventional-Commit message' — but coverage is not comprehensive (no mention of editing/amending history).	3 / 5
Completeness	It clearly answers 'what' (stage + write a Conventional-Commit message) but lacks any explicit 'Use when...' trigger clause; per the guidelines a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms users say are present ('Stage changes', 'Conventional-Commit message'), but a few common synonyms like 'git commit' or 'commit message' phrasings are not all covered.	4 / 5
Distinctiveness Conflict Risk	The 'Conventional-Commit' framing carves a clear niche with low conflict risk, though it could still overlap slightly with a generic git helper skill.	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: dlt-hub/dlt
Path: .claude/skills/commit/SKILL.md
Commit: 3ec3cfc

Reviewed: 23 hours 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.