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.
A highly actionable, well-sequenced merge workflow: every step carries executable commands, repo-specific gotchas, validation checkpoints, and feedback loops, with real attention to safety (blocker rule, shared-machine hygiene, worktree restoration). The only deductions are minor — a few trimmable restatements and tangential sections, and small organization gaps in an otherwise appropriately single-file structure.
Suggestions
Trim restated framing — e.g. drop 'Goal: the PR merged with every code-review finding fixed and CI green.' (it repeats the frontmatter description) and tighten section 0b's figure instructions to the trigger conditions plus the SHA-pinning rule, moving the how-to detail to the referenced figure skill.
Fold the trailing 'Note on gh pr edit' into the step where the description is actually edited (step 0b), or a short 'Repo quirks' section, so the file ends on the required step-7 report/cleanup checklist.
Reorder so the blocker rule (step 0) precedes the figure guidance (0b), or renumber 0b after step 1 — as written, tangential description-figure guidance interrupts the load-in/check-out/review/fix/CI/merge flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious, environment-specific facts (pg0 instance naming, the silent CONFLICTING-PR CI gap, the gh pr edit GraphQL bug, the shared stash stack) with essentially no padding, but a few minor trims exist: the frontmatter goal is restated ('Goal: the PR merged with every code-review finding fixed and CI green') and section 0b spends ~12 lines on a tangential figure nicety. This fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') better than 5 ('every token earns its place'). | 4 / 5 |
Actionability | Guidance is copy-paste ready throughout — exact gh/git/jq/pg0/lsof commands (e.g. the headSha-gated 'gh run list' snippet, 'git push origin HEAD:ci/pr-<N>-verify', 'pg0 drop --name <name> -f') — and the specific examples cover the common cases: maintainer vs. fork PR, conflicting PR, missing CI run, flaky jobs. Fully executable with placeholders appropriate to the parameterized inputs. | 5 / 5 |
Workflow Clarity | Steps 0–7 are explicitly sequenced with validation checkpoints (gate on the CI run for the pushed head SHA, judge per job, restore the worktree before merging, verify PIDs with 'ps -p' before killing) and genuine feedback loops (fix → push → back to step 5; review → fix → re-review until zero findings; 'gh run rerun --failed' for flakes). Despite being a destructive/batch workflow, validation is thoroughly present, so the workflow-clarity cap does not apply. | 5 / 5 |
Progressive Disclosure | A single-file, well-sectioned workflow with clear headers and no bundle files to reference (its references to the code-review and figure skills are repo-external, not nested bundle paths). Structure is good, but at ~180 lines a few pieces of inline detail — the trailing 'Note on gh pr edit' section and step 0b's placement before the blocker rule — could be better integrated or split, matching anchor 4 ('good structure; minor organization gaps') rather than the fully clean split of anchor 5. | 4 / 5 |
Total | 18 / 20 Passed |