Content
81%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-gated operational workflow: concrete commands, explicit merge preconditions, OID-bound merging, and verification before every irreversible step. Its weaknesses are redundancy — the same do-not-wait, PR-authorization, and prep-recovery rules are repeated across sections — and a list-indentation error that visually nests workflow steps 6 and 8 under their predecessors.
Suggestions
State each do-not-wait / monitor-after-merge rule once (in the fast-path contract) and reference it from the workflow steps instead of restating it in the intro, step 5, and step 7; this alone would cut roughly a quarter of the body.
Consolidate the prep-lane recovery rules: step 3's failure-classification and narrowest-rerun guidance is restated nearly verbatim in step 5's first gate bullet — keep the detail in step 3 and shorten the gate to a reference.
Fix the ordered-list indentation so steps 6 and 8 are top-level siblings of steps 1-5 and 7, and merge the 'Existing PR authorization' section's recheck list with step 5's pre-merge recheck to remove the duplicated login/author/head-Oid enumeration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is no concept-explanation padding (nothing teaches what CI or Netlify is), but the same rules are restated across sections — 'do not wait for remote CI, release or beta deploy checks' appears in the intro, the fast-path contract, and step 5; the PR-authorization rechecks are described twice; and the prep-recovery rules of step 3 are restated in step 5's gate list — so the ~230-line body could be tightened substantially, fitting anchor 3 ('could be tightened') rather than 4's 'minor instances'. | 3 / 5 |
Actionability | Guidance is copy-paste executable throughout: 'git status --short', 'gh pr list --head ... --json number,title,url,author', 'pnpm prep:urgent', 'corepack pnpm ship:push -m "fix: deduplicate chat start checkpoints"' (with explicit replace-the-example instruction), 'gh api user --jq .login', and 'gh pr merge <number> --squash --admin --match-head-commit <verified-head-oid>', with named recovery commands per failure lane — matching the fully executable anchor. | 5 / 5 |
Workflow Clarity | The 8-step sequence has explicit validation checkpoints and feedback loops: the 5-condition merge gate checklist, targeted prep-lane recovery, rechecking review reply coverage after every push, binding the merge to a verified head OID, verifying the merge commit in origin/main before rotation, and post-merge monitoring with a fix-on-fresh-branch loop. A formatting defect (steps ' 6.' and ' 8.' are indented as if nested under steps 5 and 7) slightly obscures the top-level sequence but introduces no validation gap, so it stays at 5 rather than 4. | 5 / 5 |
Progressive Disclosure | Scored against the actual bundle structure, which contains no references/, scripts/, or assets/ files — everything is in one well-headered SKILL.md with a clearly signaled one-level-deep external reference ('.agents/skills/ship-and-monitor/SKILL.md') and related-skill pointers. That is good structure with minor gaps (separable policy areas such as the deployment split and PR-authorization procedure are inlined in a ~230-line file), fitting anchor 4; the under-50-line no-references exception cannot lift it to 5. | 4 / 5 |
Total | 17 / 20 Passed |