commit

Writes brief conventional-commit messages, runs pre-commit checks, stages changes, commits them, and proposes splitting when the diff mixes concerns. Use when the user asks to commit, stage and commit, write a commit message, or split a change into atomic commits.

Quality

91%

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

Quality

Content

93%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.

A well-structured, token-efficient skill body with executable examples and a clear workflow including a validation checkpoint. The only minor gap is that pre-commit validation is conditional and skippable.

Suggestions

Make the pre-commit validation step less conditional — state explicitly what to do when 'make checks' is unavailable (e.g., fall back to a defined verification command) to strengthen the checkpoint.

Add a brief explicit 'verify the commit succeeded' step after committing to close the workflow loop end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a commit or conventional commits are, and every section (Message Rules, Types, Splitting Criteria, Examples) earns its place.	5 / 5
Actionability	Provides a copy-paste-ready message format, concrete good examples, a negative verbose example, the full type list, and specific commands ('make checks', 'git diff'), covering the common cases an executor needs.	5 / 5
Workflow Clarity	A clear three-step sequence with a validation checkpoint (pre-commit checks) and a feedback loop ('Pre-commit failures: ask whether to fix or proceed'), but the validation is conditional ('if available') and skippable via --no-verify, leaving a minor gap versus the top anchor.	4 / 5
Progressive Disclosure	Self-contained with no external references needed and no nested lookups; content is organized into well-signaled sections (Usage, Workflow, Message Rules, Types, Examples, Options, Notes) making navigation trivial.	5 / 5
	Total	19 / 20 Passed

Description

88%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.

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger clause. Trigger-term coverage is good but could add a few more natural synonyms to reach the top anchor.

Suggestions

Add natural synonyms such as 'make a commit' or 'git commit' to the trigger clause to broaden keyword coverage.

Consider mentioning 'atomic commits' or 'split a diff' earlier as standalone trigger phrases users may say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Writes brief conventional-commit messages, runs pre-commit checks, stages changes, commits them, and proposes splitting' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (the five concrete actions) and 'when' via a concrete 'Use when the user asks to commit, stage and commit, write a commit message, or split a change into atomic commits' clause.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('commit', 'stage and commit', 'write a commit message', 'split a change into atomic commits'), but common variants like 'make a commit' or 'git commit' are missing, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The commit-message niche is clear with distinct triggers and low conflict risk, but 'commit/stage' wording could lightly overlap with a broader git-workflow skill, so it is mostly distinct rather than unambiguously isolated.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: rikdc/ai-skills
Path: plugins/git-workflow/skills/commit/SKILL.md
Commit: cd15778

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.