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

93%

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

86%Scale 1-5

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

This is a high-quality skill that is concise, well-structured, and actionable. It efficiently communicates commit message conventions, workflow steps, and splitting criteria without over-explaining concepts Claude already knows. The examples section is particularly effective, showing both good and bad patterns. Minor improvements could be made to the workflow's feedback loops and the specificity of some conditional steps.

Dimension	Reasoning	Score
Conciseness	Every section is lean and purposeful. No unnecessary explanations of what git or conventional commits are. The examples section efficiently shows good vs bad patterns without over-explaining. The types list is a terse reference table. Every token earns its place.	5 / 5
Actionability	The workflow steps are concrete (run `make checks`, inspect staged files, commit), the message format is precise with clear rules, and examples are copy-paste ready. Minor gap: the `make checks` command is conditional ('if available') without specifying what to do if it's not available, and `git diff` usage is described rather than shown as an exact command sequence.	4 / 5
Workflow Clarity	The three-step workflow is clearly sequenced with conditional logic (nothing staged → auto-stage, mixed concerns → propose splits). Pre-commit failure handling is mentioned in Notes. However, the validation/feedback loop for pre-commit failures is only briefly noted ('ask whether to fix or proceed') rather than being an explicit checkpoint in the workflow sequence, and the splitting proposal step lacks a concrete sub-workflow.	4 / 5
Progressive Disclosure	For a skill under 100 lines with no need for external references, the content is well-organized into logical sections (Workflow, Message Rules, Types, Splitting Criteria, Examples, Options, Notes). Each section is appropriately sized and clearly labeled. No bundle files are needed for this scope.	5 / 5
	Total	18 / 20 Passed

Description

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

This is an excellent skill description that clearly articulates specific capabilities (writing commit messages, running pre-commit checks, staging, committing, and splitting diffs), uses natural trigger terms users would actually say, and includes an explicit 'Use when...' clause with concrete trigger phrases. It is well-scoped to a distinct niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: writes conventional-commit messages, runs pre-commit checks, stages changes, commits them, and proposes splitting when diff mixes concerns. Comprehensive coverage of the commit workflow.	5 / 5
Completeness	Clearly answers both 'what' (writes commit messages, runs pre-commit checks, stages changes, commits, proposes splitting) and 'when' with an explicit 'Use when...' clause listing concrete trigger phrases like 'commit', 'stage and commit', 'write a commit message', 'split a change into atomic commits'.	5 / 5
Trigger Term Quality	Includes highly natural trigger terms users would say: 'commit', 'stage and commit', 'write a commit message', 'split a change into atomic commits', 'conventional-commit', 'pre-commit checks'. These cover the natural phrases users would use.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche around git committing workflows with distinct triggers like 'conventional-commit', 'pre-commit checks', 'atomic commits', and 'stage and commit'. Unlikely to conflict with other skills due to the specificity of the commit-related domain.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

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

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.