Content
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An excellent destructive-operations skill: executable commands, a well-sequenced workflow with explicit validation and a consolidated approval gate, and tight organization without concept filler. The only nit is that the squash-merge/-D rationale is restated several times, which could be consolidated once and referenced.
Suggestions
Consolidate the squash-merge/-D rationale (currently restated in the classification table, step 5, the anti-patterns, and the example) into one canonical explanation and reference it, to shave redundant tokens.
The worked example session largely re-traces the workflow steps; consider trimming it to the non-obvious decisions (squash `-D`, missing→prune) to reduce length without losing clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and assumes Claude's git competence — it never explains what a worktree is or how `gh` works, and every section drives action. It is not a 2 because there is no concept teaching or padding; the only redundancy is the squash-merge/-D rationale, which recurs because it is a gotcha encountered at distinct decision points. | 3 / 3 |
Actionability | Provides copy-paste-ready, executable commands throughout — `git worktree list --porcelain`, `git merge-base --is-ancestor`, `gh pr list --state merged --head <branch> --json number`, `git worktree remove`, `git branch -d/-D`, `git worktree prune` — plus a concrete classification table and worked example labels. | 3 / 3 |
Workflow Clarity | A clearly sequenced 6-step workflow (enumerate → base branch → classify → consolidate approval → execute → finalize) with validation checkpoints appropriate to a destructive batch operation: `git fetch --prune origin` first, safe-delete defaults, a single consolidated `AskQuestion` gate, and a final report of removed/skipped/failed entries. | 3 / 3 |
Progressive Disclosure | No bundle files exist, so there are no broken or deeply nested references; the body is well-organized into Hard rules, Workflow, Anti-patterns, and Example session. For a single cohesive destructive-ops task, forcing an external split would be artificial, so the self-contained, clearly sectioned structure earns the top anchor. | 3 / 3 |
Total | 12 / 12 Passed |