Content
75%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 body is a well-structured, actionable batch-cleanup workflow with appropriate validation safeguards (preview, confirmation, skip-dirty, final report) and clean progressive disclosure to real bundle files and a sibling skill. It is concise and executable, with only minor trim and organization opportunities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean — tables, concise numbered steps, and code blocks with no padding of concepts Claude already knows; the only minor inefficiency is the Step 1 options-to-days table restating the inline '对应 N 天' notes, which could be trimmed. | 4 / 5 |
Actionability | Concrete executable commands are provided (git branch --show-current, the powershell/bash script invocations with -Days/-d args) and detail is delegated to the real scripts and the close-github-worktree-done skill; templated placeholders like <天数> and <N> are clearly signaled, leaving only minor gaps. | 4 / 5 |
Workflow Clarity | A clear 5-step sequence with explicit checkpoints — master-branch precondition check, preview-before-delete, user AskQuestion confirmation, skip-dirty-branches rule, continue-on-failure, and a summary report — so the destructive/batch cap does not apply; it stops short of a fix-retry feedback loop, keeping it at 4 rather than 5. | 4 / 5 |
Progressive Disclosure | Content is well-organized into signaled sections and delegates depth one level deep to real bundle scripts (cleanup-worktree.ps1/.sh, both present in ./scripts) and to the close-github-worktree-done skill rather than inlining it; minor organization gaps (the script-explanation bullets could live with the scripts) keep it just below 5. | 4 / 5 |
Total | 16 / 20 Passed |