Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and mostly concise, with a sound process outline and protective defaults, but key code blocks are pseudocode with broken variable scoping, and the destructive batch workflow lacks verification and error-recovery checkpoints. Fixing the discovery/interactive blocks and adding validation would raise both actionability and workflow clarity.
Suggestions
Replace the comment-only porcelain parsing loop with real code that populates $WORKTREES (parse 'worktree <path>' and 'branch <ref>' lines), so downstream blocks are executable.
Add explicit validation and error recovery: check `git worktree remove` exit status, handle dirty/untracked worktrees (fallback to --force or ask), verify with `git worktree list` after cleanup, and confirm before deleting remote branches instead of suppressing errors with 2>/dev/null.
Implement the interactive mode prompt (e.g., `read -r ANSWER` handling [r]emove/[k]eep/[s]kip) instead of the "# Wait for user decision" placeholder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by dense, purposeful code blocks and avoids explaining concepts Claude already knows. Minor trimming opportunities exist: flag effects appear in both the Flags table and the Quick reference table, plus a Usage section, and two full example reports could be shortened. | 4 / 5 |
Actionability | The classification, auto-mode, and disk-usage blocks give concrete commands, but the worktree discovery block is pseudocode ("# Parse worktree path and branch" with an empty loop), $WORKTREES is never populated, the dry-run loop references $BRANCH/$SIZE outside their scope, and interactive mode has no actual input mechanism. It is more than high-level hints (not 2) but not mostly-executable (not 4). | 3 / 5 |
Workflow Clarity | A clear 7-step Process sequence with pre-removal checks (protected branches, merge-base --is-ancestor, --dry-run preview), but this destructive batch workflow lacks post-removal verification and error recovery (e.g., what to do when git worktree remove fails on dirty worktrees), and auto mode silently deletes remote branches with errors suppressed. The missing validation/verification cap applies. | 3 / 5 |
Progressive Disclosure | A single-file skill with well-labeled sections and one-level links to sibling suite commands, with no nested reference chains. Minor gaps: project-specific neonctl DB-branch material is inlined without explanation, and the linked command files are outside the bundle, so it is not the clean, fully-split 5. | 4 / 5 |
Total | 14 / 20 Passed |