git-commit

Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.

Quality

81%

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.

The content is lean, actionable, and well-structured with copy-paste-ready format and concrete examples; the only gap is the absence of an explicit sequenced workflow with a feedback loop, though the checklist partially compensates.

Dimension	Reasoning	Score
Conciseness	The body is lean and tightly focused on project-specific commit guidance with no padding about what git or commits are; every section (rules, principles, format, examples, checklist) earns its place, matching the lean-and-efficient 5 anchor.	5 / 5
Actionability	It provides a copy-paste-ready HEREDOC format block plus concrete good and bad examples with explicit problem callouts and a pre-commit checklist, giving fully executable guidance that covers the common cases.	5 / 5
Workflow Clarity	The single action is unambiguous and the 'Checklist Before Committing' provides a verification checkpoint, but there is no explicit multi-step sequence or validate-fix-retry feedback loop, leaving it just below the 5 anchor.	4 / 5
Progressive Disclosure	The skill is self-contained with no need for external references and is organized into clearly labeled sections (7 Rules, Key Principles, Format, Examples, Checklist), satisfying the well-organized-sections bar for a simple single-file skill.	5 / 5
	Total	19 / 20 Passed

Description

70%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 clearly states both purpose and trigger and uses natural keywords, but its action list is abstract rather than comprehensive and the trigger could name more concrete user phrasings.

Suggestions

List concrete capabilities explicitly (e.g., 'drafts commit messages from staged diffs, enforces a 50-char imperative subject, wraps the body at 72 chars').

Broaden trigger terms to include natural variations like 'committing', 'staged changes', or 'git diff'.

Make the 'when' clause more specific, e.g., 'Use when the user asks to commit changes or write a commit message.'

Dimension	Reasoning	Score
Specificity	Names the domain ('creating git commits') and a couple of actions ('ensure commit messages follow project standards', 'Applies the 7 rules'), but the actions are somewhat abstract rather than a comprehensive list of concrete capabilities, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	It explicitly answers both what ('Applies the 7 rules for great commit messages with focus on conciseness and imperative mood') and when ('Use when creating git commits'), but the 'when' trigger could be more specific (e.g., when the user asks to commit or review staged changes), fitting the 4 anchor.	4 / 5
Trigger Term Quality	'git commits' and 'commit messages' are natural terms users would actually say, giving good keyword coverage; a few common variations like 'committing' or 'staged changes' are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The commit-message-writing niche is mostly distinct with minimal overlap risk; only a broad general-git skill could plausibly overlap, so it does not fully reach the clear-niche 5 anchor.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: cloudflare/sandbox-sdk
Path: .agents/skills/git-commit/SKILL.md
Commit: 6abf639

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.