git-commits

Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

This is a well-crafted skill that efficiently communicates conventional commits format with excellent concrete examples. The content respects Claude's intelligence and provides actionable guidance. The main weakness is the lack of explicit validation workflow for ensuring commits meet the criteria before finalizing.

Suggestions

Add a brief validation checklist or command (e.g., using commitlint) to verify commit messages meet the format before pushing

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables and examples without explaining concepts Claude already knows. No unnecessary padding or verbose explanations of what git or commits are.	3 / 3
Actionability	Provides concrete, copy-paste ready examples for each commit type, clear format templates, and specific rules. The examples show exact commit message syntax that can be directly used.	3 / 3
Workflow Clarity	The atomic commits section lists principles but lacks explicit validation steps. There's no guidance on verifying commits meet the criteria before pushing, or how to fix commits that don't follow the format.	2 / 3
Progressive Disclosure	For a skill of this scope (~80 lines), the content is well-organized with clear sections. The single reference to external docs (migration guide) is appropriate and one level deep.	3 / 3
	Total	11 / 12 Passed

Description

89%

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 a solid skill description with explicit 'Use when' guidance and good trigger terms that developers would naturally use. The main weakness is that it describes concepts and principles rather than listing specific concrete actions the skill enables. Adding action verbs like 'generate', 'validate', or 'format' would strengthen specificity.

Suggestions

Add specific concrete actions like 'Generates commit messages', 'Validates commit format', or 'Structures atomic commits' to improve specificity

Dimension	Reasoning	Score
Specificity	Names the domain (git commits) and mentions some concepts (conventional commits format, atomic commit principles, type prefixes, semantic versioning), but doesn't list specific concrete actions like 'generate commit messages', 'validate commit format', or 'structure commits'.	2 / 3
Completeness	Clearly answers both what (git commit best practices with conventional commits format and atomic commit principles) AND when (Use when committing code) with explicit trigger guidance about ensuring clear commit history.	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'git commit', 'committing code', 'commit history', 'conventional commits', 'semantic versioning'. These are terms developers naturally use when seeking commit guidance.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on git commit conventions and formatting. The specific mentions of 'conventional commits', 'type prefixes', and 'atomic commit principles' distinguish it from general git skills or code review skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.