commit

Create a git commit with conventional commit format. MUST use anytime you want to commit changes.

Quality

64%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and well-structured for a simple self-contained skill, but suffers from redundant step sections and a missing error-recovery loop that keep conciseness and workflow clarity at the mid anchor.

Suggestions

Merge '## Instructions' and '## Execution Steps' into one numbered workflow; the current duplication (both open with git status/git diff) wastes tokens.

Add an explicit error-recovery loop after the commit, e.g. 'If the commit fails, review the error, fix, and re-run git commit', to strengthen the verification checkpoint.

Trim the conventional-commit type list to the few Claude would not reliably recall, or move the full list to a reference file, since Claude already knows feat/fix/docs/style.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, but '## Instructions' (3 steps) and '## Execution Steps' (6 steps) duplicate each other — both open with git status/git diff — and the conventional-commit type list restates knowledge Claude already has, so it is not fully tight.	2 / 3
Actionability	It gives fully executable commands (`git status`, `git diff`, `git log --oneline -5`, `git add <file1> <file2>`, `git commit -m "<type>: <description>"`) plus concrete copy-paste-ready examples, matching the executable anchor.	3 / 3
Workflow Clarity	Execution Steps 1-6 provide a clear sequence with a verification checkpoint (step 6 runs git status to confirm), but there is no error-recovery feedback loop and the redundant Instructions/Execution Steps pair creates mild ambiguity about which flow to follow.	2 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the skill is under 50 lines, self-contained, and organized into clear sections (Instructions, Conventional Commit Format with Types/Rules/Examples, Execution Steps), so the simple-skill anchor gives it a 3.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 answers both what and when with an explicit trigger, but its second-person phrasing triggers the voice penalty and its trigger is too broad to be distinctive.

Suggestions

Rewrite in third person and replace the second-person trigger with a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to commit changes, write a commit message, or save staged work'.

Add concrete actions beyond 'Create a git commit' — e.g. 'analyzes the diff, stages selected files, and writes a conventional commit message' — to lift specificity.

Narrow the trigger so it fires for conventional-format commit requests specifically, reducing overlap with generic commit helpers.

Dimension	Reasoning	Score
Specificity	The description names one concrete action ('Create a git commit with conventional commit format') which would anchor at 2, but the trigger clause uses second person ('MUST use anytime you want to commit changes'), so the rubric's voice penalty reduces specificity by one to 1.	1 / 3
Completeness	It states what ('Create a git commit with conventional commit format') and an explicit when ('MUST use anytime you want to commit changes'), satisfying both halves with an explicit trigger, so it is not capped at 2.	3 / 3
Trigger Term Quality	'commit' / 'commit changes' are natural terms a user would say, but coverage is thin and misses common variations like 'make a commit', 'save changes', or 'write a commit message', so it sits at the 'some relevant keywords' anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	'git commit with conventional commit format' is a recognizable niche, but the trigger 'anytime you want to commit changes' is broad enough to fire for any commit request and overlap with generic commit helpers, so it is not clearly conflict-free.	2 / 3
	Total	8 / 12 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: windmill-labs/windmill
Path: .agents/skills/commit/SKILL.md
Commit: 33d2845

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