Lean and efficient; it defines only the skill-owned concept of a standalone commit and otherwise assumes Claude's competence, with no padding about what git or commits are. Every section (standard, checks, heuristics, anti-patterns) earns its place.

Provides concrete executable guidance: the one-sentence claim template, a specific `git diff --staged` command in the staging workflow, and concrete commit-message anti-patterns with 'Problem'/'Better' pairs.

The Staging Workflow is a clear 6-step sequence with an explicit validation checkpoint (step 5: run focused verification) and a re-read feedback loop ('re-read the staged diff and ask whether the claim is still honest'), backed by the Acceptance Checks table as a checklist.

SKILL.md is a concise overview that defers the detailed wave procedure to a single clearly signaled, one-level-deep reference (references/splitting-into-ordered-waves.md), which exists as a real bundle file.

Lists multiple concrete actions — 'Make commits reviewable and auditable as self-contained units', 'order multi-file changes into atomic dependency-ordered waves', and 'deciding whether a commit is too broad, too tiny, incomplete, or hard to revert' — rather than vague language.

Explicitly answers both what (make commits reviewable/auditable and order them into dependency-ordered waves) and when via the explicit 'Use when planning commits…' clause.

Includes natural phrases users would actually say — 'split this into commits', 'break this up', 'commit strategy', 'splitting work into waves', 'staging changes', 'reviewing branch history' — giving good coverage of common variations.

Occupies a clear niche (commit boundary shaping and dependency ordering) with distinct triggers unlikely to fire for unrelated skills; the reference to the separate git skill keeps formatting concerns out of scope.