CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit

Generate a commit message and commit staged changes using git commit -s -S.

Quality

78%

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

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 content is a tightly written, fully executable procedure with concrete commands, explicit formatting rules, and good edge-case handling for a simple single-purpose skill. Its only minor weaknesses are an enumeration of Conventional Commits types Claude already knows and the lack of a failure-recovery path for signed commits.

DimensionReasoningScore

Conciseness

The body is lean: six numbered steps of pure instruction with no concept explanations, and the parenthetical about the Signed-off-by trailer is genuinely useful. The one trim candidate is the enumerated Conventional Commits type list ('Valid types: feat, fix, docs, ...'), which Claude already knows — a minor instance of over-explanation matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Every step is an exact, executable command ('git diff --staged', 'git log --oneline -5', 'git commit -s -S -m "<subject>" -m "<body>"') with explicit format constraints (72 chars, lowercase, no trailing period) and all common cases covered (nothing staged, branch pattern match/mismatch, no tracking issue). This matches anchor 5: fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear 1-6 sequence with pre-validation checkpoints (stop when nothing is staged, branch pattern check with a fallback user prompt). It falls short of anchor 5 because there is no error-recovery feedback loop — e.g., what to do if the -S signed commit fails due to missing GPG key configuration.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no external references needed; the simple-skill exception applies and the well-organized numbered steps merit a 5. All bundle directories (references/, scripts/, assets/) are absent and no referenced paths are cited, so the single-file structure is appropriate.

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, in third person, and states concrete actions with an exact command, giving it good trigger terms and reasonable distinctiveness. Its main weakness is the complete absence of a 'when to use this' trigger clause, which caps completeness, and its action coverage is narrow relative to what the skill body actually does.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to commit, commit staged changes, or create a commit message.'

Broaden the capability coverage to match the body, e.g. mention analyzing the staged diff and repo commit style when generating the message.

Include natural synonyms such as 'sign off' or 'DCO' to improve trigger coverage for the -s -S behavior.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ('Generate a commit message' and 'commit staged changes') plus the exact command form ('using git commit -s -S'), but coverage is not comprehensive — no mention of diff analysis, message style, or sign-off semantics. It sits between anchor 3 (1-2 concrete actions) and anchor 4 (several actions with minor gaps), and is closer to 3 since only two real actions are listed.

3 / 5

Completeness

It clearly answers 'what' (generate a commit message and commit staged changes) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural phrases users would actually say are present: 'commit', 'commit message', 'staged changes', 'git commit'. A few natural terms are missing (e.g., 'sign off', 'DCO', 'sign commit'), so it matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'staged changes' and the specific 'git commit -s -S' invocation make it mostly distinct from unrelated skills, though it overlaps with generic commit-message-generation skills. Minor overlap risk with closely related skills matches anchor 4; anchor 5 would require distinct trigger phrases that are absent.

4 / 5

Total

14

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

linuxfoundation/crowd.dev

Path

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