commit-all

Use this skill when the user asks to "commit all", "commit everything", or wants all outstanding changes committed. Groups unrelated changes into separate, well-described commits instead of one catch-all commit.

Quality

90%

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

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

An excellent, lean instruction-only skill: concrete git commands, a well-sequenced workflow with explicit verification, and sensible hard rules (no `git add -A`, no push, secret detection). The only meaningful gap is the absence of a recovery loop after the verification step (e.g., what to do if the tree is not clean).

Suggestions

Add a brief recovery step after verification, e.g. 'If `git status` still shows changes, identify the remaining group(s) and commit them the same way.'

Include one short example commit message (subject + body + trailer) so the message style rules are demonstrated, not just described.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: no explanation of git basics, no padded prose, and every rule ("Never use `git add -A`", "Keep the subject line under 72 characters", "Do not push") adds non-obvious guidance. It assumes Claude's competence; not 4 because there are no sections that could be trimmed without losing information.	5 / 5
Actionability	Fully concrete commands throughout: `git status`, `git diff` (staged + unstaged), `git add <file> ...`, `git log --oneline -10`, and `git log --oneline -n <N>` are all executable as written, plus specific message rules (imperative mood, <72 chars, Co-Authored-By trailer). For an instruction-only skill this is copy-paste-ready guidance; not 4 because there are no gaps for the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence (survey → group → order → commit per group → verify) with an explicit validation step ("run `git status` to confirm the tree is clean"), so the batch-operation cap at 3 does not apply. Not 5 because there is no error-recovery feedback loop — no guidance on what to do if the tree is not clean or a group was missed after verification.	4 / 5
Progressive Disclosure	The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ exist), and is organized into well-separated sections (Goal, Workflow, Commit Message Rules, Hard Rules). Per the rubric's simple-skill note, a short single-purpose skill with well-organized sections scores 5 with no external references needed.	5 / 5
	Total	19 / 20 Passed

Description

83%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 with an explicit 'Use when...' trigger, natural user phrasing, and a clear statement of what the skill does and how it differs from a naive single-commit approach. The only weaknesses are modest synonym coverage and slight overlap risk with general git-commit skills.

Suggestions

Add one or two common trigger variations such as "commit all my changes" or "stage and commit everything" to broaden natural-term coverage.

Sharpen the boundary against a generic commit skill, e.g. 'Use when the user wants EVERYTHING committed, not when asking to commit specific files.'

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "commit all outstanding changes" is implied via the trigger, "Groups unrelated changes into separate, well-described commits" names the grouping and message-quality behavior. It falls between anchor 3 (1-2 actions) and anchor 5 (comprehensive coverage) because coverage gaps exist (ordering, no-push, secret handling are not mentioned), landing at 4.	4 / 5
Completeness	Explicitly answers both questions: "Use this skill when the user asks to 'commit all'..." is a concrete 'when', and "Groups unrelated changes into separate, well-described commits instead of one catch-all commit" is a clear 'what'. This matches anchor 5 with concrete trigger phrases; not 4 because the 'when' is fully explicit, not merely present.	5 / 5
Trigger Term Quality	Includes natural phrases users would actually say: "commit all", "commit everything", and "wants all outstanding changes committed". Not 5 because common variations like "commit all my changes", "stage and commit everything", or "just commit it all" are absent; clearly above 3 since the terms present are exactly the phrases a user would utter, not generic jargon.	4 / 5
Distinctiveness Conflict Risk	"commit all" / "commit everything" form a clear niche distinct from generic git or commit-message-writing skills, and "instead of one catch-all commit" delineates the boundary. Not 5 because the broader clause "wants all outstanding changes committed" leaves minor overlap risk with a general commit skill on requests like "commit my changes".	4 / 5
	Total	17 / 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: spacedriveapp/spacebot
Path: .agents/skills/commit-all/SKILL.md
Commit: 5c2ee47

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