CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 tight, highly actionable procedure with explicit sequencing, stop conditions, and error-recovery paths for each git edge case. The only improvement space is trimming the few rationale sentences in the stage-and-commit step.

DimensionReasoningScore

Conciseness

The body is dense procedural policy with no explanation of concepts Claude already knows, but a few passages could be trimmed — the trailing whitespace-cleanup sentence and the two rationale paragraphs after the commit command (why -F, why the trailing path list) state reasoning that could be shortened without losing the constraint.

4 / 5

Actionability

Fully executable guidance throughout: exact context-gathering commands with an interpretation table for non-zero exits, copy-ready `git add file1 file2 file3` and `git commit -F <message-file> -- file1 file2 file3` invocations, and concrete bad/good subject examples covering common cases.

5 / 5

Workflow Clarity

An explicit 0–7 sequence with validation checkpoints (step 7 `git status` confirmation, re-reading branch and staged set before committing) and error-recovery loops for every failure mode: unborn repo, detached HEAD, missing origin/HEAD with a fallback chain, and branch-name collisions.

5 / 5

Progressive Disclosure

A single-file skill with clean Context/Workflow sectioning, no nested references, and no content that belongs in a separate file — every rule present (message policy, staging constraints, co-authoring) applies on every invocation, so inline placement is correct.

5 / 5

Total

19

/

20

Passed

Description

86%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 concise, third-person description that explicitly answers both what it does and when to use it with natural trigger phrasing. Its only weaknesses are modest action coverage (single action) and unbounded scope relative to the related push/PR skill referenced in the body.

DimensionReasoningScore

Specificity

"Create a git commit with a clear, value-communicating message" names the domain and one concrete action with a quality bar, but offers no additional actions (e.g., splitting logical commits or matching conventions), matching the "1-2 concrete actions, not comprehensive" anchor rather than the several-action anchor at 4.

3 / 5

Completeness

Both halves are explicit: "Create a git commit with a clear, value-communicating message" answers what, and "Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message" answers when with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

The description includes comprehensive natural trigger phrasing for this domain — "commit/save staged or unstaged changes" covers commit, save, staged, and unstaged variations users actually say; no natural synonym for this task is missing (file extensions are not applicable to git).

5 / 5

Distinctiveness Conflict Risk

The commit-only niche is clear, but the description does not itself bound the scope against its sibling push/PR skill, so a request like "commit and push" would still match — minor overlap risk with a closely related skill rather than the minimal-conflict top anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.