commit

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

Quality

80%

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

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 highly actionable with concrete commands and examples, and well-organized for a simple skill. The main gap is redundancy between the Instructions and Execution Steps sections and the absence of an error-recovery loop.

Suggestions

Merge the 'Instructions' and 'Execution Steps' sections into one canonical sequenced workflow to remove redundancy.

Add a brief feedback step for failure cases (e.g., if the commit fails due to no staged changes or a hook rejection, fix and retry).

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows, but the 'Instructions' and 'Execution Steps' sections overlap noticeably (both cover status/diff, staging, and committing), which could be consolidated.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands (git status, git diff, git add <file>, git commit -m, git log) plus concrete commit-message examples covering the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence ends with an explicit verification step ('Run git status to verify the commit succeeded'), but there is no error-recovery feedback loop if staging or the commit fails.	4 / 5
Progressive Disclosure	A simple, single-purpose skill (~50 lines) with no need for external references, organized into clear sections (Instructions, Conventional Commit Format, Execution Steps); well-structured and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

73%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 third-person, concise, and clearly answers both what the skill does and when to use it, with a distinct niche. Its main weakness is single-action coverage and limited trigger-term variation.

Suggestions

Expand the trigger clause to list a few natural user phrases (e.g., 'Use when the user asks to commit, stage and commit, or write a commit message').

Add 1-2 more concrete actions (e.g., 'stage specific files and write a conventional commit message') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('git commit', 'conventional commit format') and one concrete action ('Create a git commit'), but coverage is a single action rather than a list; appropriate for a single-purpose skill yet not comprehensive.	3 / 5
Completeness	Explicitly states what ('Create a git commit with conventional commit format') and when ('MUST use anytime you want to commit changes'), but the trigger is a single clause rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural phrase 'anytime you want to commit changes' that a user would say, but lacks variations like 'stage and commit' or 'git commit'; good but not exhaustive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	'git commit with conventional commit format' is a clear, narrow niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 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: 74af4ed

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