CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit

Create a git commit with a summary of changes

Quality

75%

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 ./test/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 tight, executable workflow with concrete commands and a useful staged-files guard. Its only real gap is the absence of an example commit-message format, which would lift actionability.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no over-explanation (e.g., no lectures on what git is), so every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete copy-paste commands (`git diff --staged`, `git status`, `git commit -m "<message>"`) are provided, but step 2 ("Write a concise commit message") lacks any example message format, leaving a minor gap at anchor 4.

4 / 5

Workflow Clarity

A clear numbered sequence with an explicit staged-files checkpoint is present; git commit is not a destructive/batch operation so the cap does not apply, though a post-commit verification step is missing, fitting anchor 4.

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no need for external references, and the body is well-organized with a heading and numbered steps, qualifying for anchor 5 under the simple-skill guideline.

5 / 5

Total

18

/

20

Passed

Description

53%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 clearly states a single concrete capability but lacks any explicit "when to use" trigger guidance and omits common synonyms. It is distinct enough to avoid most conflicts yet would benefit from a Use-when clause.

Suggestions

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

Include natural synonyms such as "commit message" and "staged changes" to improve trigger-term coverage.

Optionally mention additional concrete actions (e.g., reviewing the diff) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Create a git commit with a summary of changes" names the domain and one concrete action (committing), matching anchor 3 for domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The "what" (create a git commit) is clear, but there is no "Use when..." trigger clause, so completeness is capped at 3 per the missing-trigger-guidance rule and matches anchor 3.

3 / 5

Trigger Term Quality

"git commit" and "summary of changes" are natural terms a user might say, but common synonyms like "commit message", "diff", or "staged changes" are missing, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

"Create a git commit" carves a clear niche distinct from other version-control tasks, but the absence of explicit trigger guidance leaves minor overlap risk with related git skills, fitting anchor 4.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Windy3f3f3f3f/claude-code-from-scratch

Path

test/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.