Content
92%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 operator procedure: hard safety rules up front, a fully executable gh-based pipeline with validation checkpoints and failure branches for every risky step, and a crisp output contract. The only flaw is repetition — the signed-merge-commit rationale is stated several times where one authoritative statement plus back-references would do.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific, non-inferable knowledge (ADR-0044 signing rationale, migration journal collisions, workflow names) and assumes Claude's competence with gh/CI. However, the web-flow-signature fact is restated roughly five times (intro, hard rules 3 and 5, steps 4a and 4c) and the /pr-iterate complementarity appears twice, which is over-explanation that could be trimmed. | 4 / 5 |
Actionability | Fully executable throughout: exact gh commands with flags, JSON fields, and jq filters ('gh pr list --state open --json number,title,isDraft,reviewDecision,mergeable,mergeStateStatus,headRefName', 'gh api -X PUT "repos/{owner}/{repo}/pulls/$PR/update-branch"', 'gh pr merge "$PR" --merge'), named workflows to watch, and a concrete output template. Common cases including stale-PR and failure paths are covered. | 5 / 5 |
Workflow Clarity | A clearly sequenced 5-step procedure with explicit validation checkpoints (per-PR green verification, 'gh pr checks "$PR" --watch' after update-branch, watching migrate-db.yml and release.yml before the next merge) and explicit error-recovery branches at each step (red after update → skip and route to /pr-iterate; merge rejected → stop unless transient; migrate-db failure → hard stop). The batch-operation cap does not apply because feedback loops are present. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so structure is judged on organization: the body is a cohesive ~95-line procedure with clear sections (What this does, Hard rules, Procedure, Output format) and a well-signaled one-level-deep Cross-references section pointing to ADR-0077/ADR-0044/ADR-0035 and the sibling skills. Nothing inlined here belongs in a separate file; navigation is easy. | 5 / 5 |
Total | 19 / 20 Passed |