Conciseness

The body is a lean ruleset with zero padding: it never explains what git is or how it works, and even the single motivating sentence ('one `git checkout -- .` erased two days of work') earns its place by justifying the rules' rigidity. Every section is actionable content that assumes Claude's competence.

Actionability

Fully concrete guidance throughout: exact commands (`git status`, `git diff <file>`, `git stash push -m "<why>"`, `git revert <sha>`, `git diff --stat`), a table enumerating each destructive command with precisely what it destroys, a safe-defaults list, and a copy-paste-ready suggested-commit example. Nothing is left as vague direction.

Workflow Clarity

Although this skill governs destructive operations, explicit validation is present everywhere: the pre-command sequence (status → stop if dirty → ask), the diff-before-discard rule with its --stat fallback for long diffs, the revert workflow's read-diff-then-edit steps, and two checklists with verification items ('git status ran and I read it', 'no uncommitted work is in the blast radius, or the user approved'). The destructive-operation cap therefore does not apply, and the content matches the anchor's 'explicit validation steps... checklists' description.

Progressive Disclosure

The skill needs no external references — it is a compact single-purpose ruleset (~83 lines) with clear section headers (before-any-command, approval table, revert-as-edit, diff-before-discard, safe defaults, checklists) that make navigation trivial, and no content that belongs in a separate file. The bundle contains only logo assets, none of which are needed for instruction.

Specificity

The description lists multiple specific concrete actions — 'Requires git status and git diff before any command that discards changes, treats "revert" and "undo" as manual edits, and never runs reset, checkout, clean, stash drop, or force push without explicit approval' — covering both the required pre-checks and the gated commands comprehensively, matching the anchor-5 example's level of coverage.

Completeness

It explicitly answers both what ('Stops an agent from destroying uncommitted work with git. Requires git status and git diff... never runs reset, checkout, clean, stash drop, or force push without explicit approval') and when ('Use when a task involves reverting, undoing, resetting, cleaning, rebasing, or force pushing...'), structurally matching the anchor-5 example exactly.

Trigger Term Quality

The trigger phrase 'Use when a task involves reverting, undoing, resetting, cleaning, rebasing, or force pushing' covers the natural verbs a user would actually say, plus 'before any git command in a repo with uncommitted changes'. Only trivial synonyms (e.g., 'rollback') are absent, which does not pull it below the comprehensive anchor.

Distinctiveness Conflict Risk

The core niche (safety around destructive git operations) is clearly distinct with specific triggers, but the fallback clause 'or before any git command in a repo with uncommitted changes' makes it liable to fire alongside any git-related skill. That is minor overlap risk with closely related skills (anchor 4), not the minimal-conflict clarity of anchor 5.