commit-staged

Generates and commits conventional-commits messages by analyzing staged git diffs — fast and fork-context safe. Use when the user asks to commit staged changes, needs a type-scope-description message generated from the current diff, or wants scope selection guidance and pre-commit hook handling.

Quality

85%

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

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

Highly actionable and well-sequenced with validation and a hook-blocked feedback loop, but it carries generic best-practice padding and is a long monolith that could offload detailed scope guidance to a reference file. The core commit-generation guidance is strong.

Suggestions

Trim generic advice Claude already knows (the 'Best practices' bullets like 'Atomic commits' and 'Write for humans') and the tangential 'Amending commits' / interactive 'git add -p' sections to tighten conciseness.

Move the extensive Scope Rules section (anti-patterns table + by-domain/by-layer/by-plugin examples) into a references/ file (e.g. SCOPE.md) and keep a brief summary + link in SKILL.md to improve progressive disclosure.

Consolidate the redundant guidance between 'Commit message guidelines', 'Best practices', and the 'Commit message checklist' into a single checklist to reduce overlap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but several sections pad with knowledge Claude already has ('Atomic commits - One logical change per commit', 'Write for humans - Future you will read this') and tangential sections (amending, 'git add -p' interactive helper) could be trimmed; not a 4 because the over-explanation is more than minor.	3 / 5
Actionability	Fully executable commands throughout ('git diff --staged', 'git commit -m', 'uv run prek run', 'git commit --amend') with concrete copy-paste-ready format examples covering common commit types; not below 5 because the common cases are specifically covered.	5 / 5
Workflow Clarity	Clear sequence with explicit validation (the opening 'uv run prek run' pre-commit check), a pre-commit checklist, and a feedback/escalation loop for blocked hooks ('stop, and announce your intended commit message... requires a linting-agent').	5 / 5
Progressive Disclosure	Well-organized with clear section headers, but it is a ~244-line monolith with no bundle files, and content that could be split out (the extensive scope rules, anti-patterns table, and example sets) is fully inlined; not a 4 because the lack of any file splitting and length go beyond minor organization gaps.	3 / 5
	Total	16 / 20 Passed

Description

92%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 clearly states both the capability and concrete trigger conditions, with good natural-language keywords and a distinct niche. The only minor gap is synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generates and commits conventional-commits messages by analyzing staged git diffs', 'scope selection guidance and pre-commit hook handling' — giving comprehensive coverage of its niche; not a 4 because coverage is thorough rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what ('Generates and commits conventional-commits messages by analyzing staged git diffs') and when ('Use when the user asks to commit staged changes...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ('commit staged changes', 'current diff', 'scope selection guidance', 'pre-commit hook'), but a few common synonyms are missing, so it falls short of the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche — conventional commit messages from staged git diffs with scope guidance — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: Jamie-BitFlight/claude_skills
Path: .claude/skills/commit-staged/SKILL.md
Commit: 3e0b2af

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.