contextual-commit

Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.

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

The canonical home for this skill is contextual-commit in berserkdisruptors/contextual-commits

Quality

Content

82%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, actionable skill body with concrete examples and a clear pre-commit workflow. The main weaknesses are minor verbosity in the framing and Git Workflows sections and no progressive file splitting for the lengthy examples.

Suggestions

Tighten or remove the 'The Problem You Solve' framing section and the 'Git Workflows' merge/rebase notes, which restate git behavior Claude already knows.

Consider moving the four full commit-message examples into a separate references file (e.g. EXAMPLES.md) to keep SKILL.md a lean overview, signaling it with a one-level-deep link.

Add an explicit self-check step in the 'Before You Write the Commit' workflow (e.g., 'verify every staged file is accounted for by an action line or consciously omitted') to strengthen the validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and focused on the novel action-line format, but sections like 'The Problem You Solve' (motivational framing) and 'Git Workflows' (explaining merge/rebase behavior Claude already knows) are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides a concrete format spec, copy-paste-ready commit message examples across simple/moderate/complex/pivot cases, and a specific command (`git diff --cached --stat`), fully executable guidance covering common cases.	5 / 5
Workflow Clarity	'Before You Write the Commit' gives a clear numbered sequence with the staged-changes check as an explicit checkpoint and a Rules checklist, but it lacks an explicit validation/retry feedback loop (acceptable here since commits are not destructive or batch).	4 / 5
Progressive Disclosure	No bundle files exist; all content is inline in SKILL.md with well-organized section headers and easy navigation. Structure is good, though at ~196 lines the long Examples section could in principle be split out.	4 / 5
	Total	17 / 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, specific description that clearly states what the skill does and when to use it, with concrete natural-language triggers. The only gap is slight overlap risk with generic commit-message skills and a few missing common trigger synonyms.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('capture intent, decisions, and constraints', 'structured action lines in the commit body that preserve WHY') covering the skill's behavior comprehensively, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers both what ('Write contextual commits that capture intent, decisions, and constraints... structured action lines') and when ('Use when committing code, finishing a task, or when the user asks to commit') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('Use when committing code, finishing a task, or when the user asks to commit'), but common variations like 'git commit', 'write a commit message', or 'stage changes' are missing, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'contextual commits' / 'Extends Conventional Commits with structured action lines' niche is well-defined and distinct, but trigger phrases like 'committing code' overlap with a generic commit-message skill, leaving minor conflict risk.	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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: yamadashy/repomix
Path: .agents/skills/contextual-commit/SKILL.md
Commit: c898ff0

Reviewed: about 13 hours 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.