commit

Create a git commit with conventional commit format. MUST use anytime you want to commit 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 ./.agents/skills/commit/SKILL.md

Quality

Content

78%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 lean, fully executable checklist with concrete commands, a clear format specification, and real examples. Its only real flaws are the duplicated step lists between the Instructions and Execution Steps sections and the absence of an error-recovery loop after the final verification step.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and rules, but the "Instructions" and "Execution Steps" sections duplicate the same status/diff/stage/commit sequence, and the opening line restates the title — it could be tightened into one list.	3 / 5
Actionability	Every step is copy-paste ready: `git status`, `git diff`, `git log --oneline -5`, `git add <file1> <file2>`, and `git commit -m "<type>: <description>"`, plus five realistic example messages covering the common commit types.	5 / 5
Workflow Clarity	A clear six-step sequence ends with an explicit verification checkpoint ("Run `git status` to verify the commit succeeded"), but there is no feedback loop for error recovery (e.g. what to do if the commit fails or wrong files were staged), so it falls short of anchor 5.	4 / 5
Progressive Disclosure	This is a short, single-purpose skill with no bundle files; the sections (Format, Types, Rules, Examples, Execution Steps) are well-organized and everything is appropriately inline, satisfying the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

57%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 answers what and when explicitly and stays concise, but the when-clause is tautological, natural trigger synonyms ("commit message", "make a commit") are absent, and the second-person phrasing costs it specificity. It is serviceable but below the quality of the reference good examples.

Suggestions

Replace the tautological when-clause with concrete trigger phrases, e.g. "Use when the user asks to commit, save, or check in changes, or when changes are staged and ready to commit."

Remove the second-person phrasing ("anytime you want to commit changes") in favor of third-person voice, e.g. "Use whenever committing changes to a git repository."

Add one more concrete capability and natural synonyms, e.g. "Generates conventional commit messages (feat, fix, chore) and stages only the relevant files" — this covers commit-message writing, a phrase users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Create a git commit with conventional commit format") but coverage is not comprehensive, matching anchor 3; the second-person clause "MUST use anytime you want to commit changes" triggers the 1-point specificity penalty, landing at anchor 2's territory.	2 / 5
Completeness	Both what ("Create a git commit with conventional commit format") and when ("MUST use anytime you want to commit changes") are explicitly present, but the when is tautological rather than offering concrete trigger phrases, so it does not reach anchor 5.	4 / 5
Trigger Term Quality	Relevant keywords like "git commit", "conventional commit", and "commit changes" are present, but common natural variations users say — "commit message", "make a commit", "save changes" — are missing, matching the anchor for some relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	"Create a git commit with conventional commit format. MUST use anytime you want to commit changes" carves a clear niche (committing code changes) with mostly distinct triggers and only minor overlap risk against closely related git skills.	4 / 5
	Total	13 / 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: windmill-labs/windmill
Path: .agents/skills/commit/SKILL.md
Commit: af42c47

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