ce-commit

Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

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

92%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 high-quality, dense, and executable skill body that pairs concrete commands and examples with a well-sequenced, checkpointed workflow. The only minor weakness is one justification paragraph that could be trimmed for token efficiency.

Suggestions

Tighten the 'trailing path list is load-bearing' paragraph to a single sentence so every remaining token clearly earns its place.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (PowerShell caveat, command table), with only the trailing-pathlist justification paragraph being slightly more explanation than strictly needed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully lean level 5.	4 / 5
Actionability	Concrete commands in the Context table, bad/good message examples, and a copy-paste-ready heredoc commit template make the guidance fully executable and cover the common cases, matching the top anchor.	5 / 5
Workflow Clarity	A clearly numbered 0–7 sequence with explicit validation checkpoints (stop-if-clean in step 1, re-read branch/staged set before committing, confirm via git status in step 7) and a re-check feedback loop matches the anchor for clear sequencing with explicit validation.	5 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clearly headed sections (Context, Workflow) plus a command table and code block; for a single-purpose skill with no need for external references, this well-organized structure earns the top anchor.	5 / 5
	Total	19 / 20 Passed

Description

78%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 description that clearly states both the capability and explicit usage triggers with natural user phrasing. It is slightly limited by naming only one concrete action and not disambiguating from sibling commit-related skills.

Suggestions

Consider listing one or two more concrete actions (e.g., 'split changes into logical commits, draft a repo-appropriate message') to lift specificity above the single-action anchor.

Add a brief disambiguation cue in the description itself (e.g., 'local commits only — not push or PR') to reduce overlap risk with a sibling push-pr skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('git commit') and one concrete action ('Create a git commit with a clear, value-communicating message'), but does not enumerate multiple specific actions, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' level above.	3 / 5
Completeness	It explicitly answers both what ('Create a git commit with a clear, value-communicating message') and when ('Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger terms like 'commit', 'save', and 'staged or unstaged changes' give good keyword coverage with synonyms a user would actually say, falling just short of the comprehensive-synonym-plus-extension anchor at 5.	4 / 5
Distinctiveness Conflict Risk	The commit-only niche is mostly distinct with minimal conflict risk, but the description does not disambiguate from the sibling push-pr skill (that disambiguation lives only in the body), leaving minor overlap risk.	4 / 5
	Total	16 / 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: EveryInc/compound-engineering-plugin
Path: skills/ce-commit/SKILL.md
Commit: 0e758b6

Reviewed: 4 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.