Content
88%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.
An excellent operational skill: fully executable commands, an explicitly gated multi-step workflow with hard stops and validation for destructive batch operations, and clearly delegated external concerns. The only deductions are minor redundancy from the checklist and procedural detail that could live in a reference file.
Suggestions
Trim the closing checklist to the few non-obvious invariants (or drop it), since each item restates a body rule verbatim — that redundancy costs ~8 lines.
Move the dual refresh histories (native cascading rebase vs incremental merge-forward, including the conflict/push procedure) into a references/refresh.md file and keep only the decision rule inline, shortening the body.
Split long compound sentences in 'Refresh only when needed' (e.g., the sync/rebase/push sentence) into short imperative steps to improve scanability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence (no PR/git primer), and nearly every sentence adds a constraint or command. Not a 5 because the closing checklist duplicates ~8 lines of body rules and some compound sentences could be tightened; not a 3 because no passage explains concepts Claude already knows and padding is minimal. | 4 / 5 |
Actionability | Every step ships an executable command with real flags and JSON field lists: `gh pr view <pr> --json ...`, a complete copy-paste GraphQL query for PullRequest.stack, `gh stack link --base <trunk> ...`, `gh stack merge <stack-number> --yes --merge`, `gh stack sync`/`rebase`/`push`, and a `gh pr list --state open --base <branch> --json number --jq length` dependent-count check. Placeholders are the only un-filled parts, appropriately so. | 5 / 5 |
Workflow Clarity | The sequence is explicit and gated: version check → live metadata fetch → stack membership via GraphQL → link missing members → optional refresh → preflight ('Require every selected PR to be open, non-draft...') → merge → verify MERGED → guarded branch deletion. Destructive/batch operations (history rewrite, stack merge, branch deletion) each have validation checkpoints and stop-and-ask feedback loops ('Anything other than 0 blocks deletion', 'hard-stop', 'cancel and ask'), plus a final checklist. | 5 / 5 |
Progressive Disclosure | Sections are clear and external material is well signaled one level deep (AGENTS.md for merge-forward/rebase history, the stack review guide for review-fix propagation, the incremental-retargeting note), with no buried or nested references. Not a 5 because the ~127-line body inlines two long procedural blocks (stack linking rules and the dual refresh histories) that carry near-reference-level detail a separate file could own. | 4 / 5 |
Total | 18 / 20 Passed |