Content
67%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 well-structured, actionable review-pipeline skill with concrete commands and clear phase sequencing. Its main weakness is conciseness: the Rules section and project-rationale material duplicate content already covered in the phase descriptions.
Suggestions
Remove or fold the '## Rules' section into the phases — its nine rules restate the phase content (fixed panel, changed-files-only, isolated-then-adversarial, confidence ≥ 80%, verify-before-post, harness permission, single comment), cutting significant duplication.
Trim the '## Why this is a project skill' rationale and the repeated substrate self-justifications (e.g. 'declining /conduct here IS that warrant relaying'); these explain protocol internals Claude does not need to execute the review.
State the 'isolated → adversarial' mechanism and the 'fixed formal panel' once (in Phase 2) and reference it from the Pipeline Overview and Rules, instead of re-explaining it in all three places.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and free of basic-concept padding, but the '## Rules' section restates the phase descriptions and the 'Why this is a project skill' rationale plus substrate-meta jargon ('warrant relaying') add noticeable duplication that could be tightened. | 3 / 5 |
Actionability | Provides concrete executable commands — 'gh pr diff {N}', 'git diff HEAD', 'gh pr view --json number', 'gh api repos/{owner}/{repo}/issues/{N}/comments --input -', 'jq --rawfile' — with only minor gaps (the jq/heredoc composition is not given as a single ready-to-run line). | 4 / 5 |
Workflow Clarity | A clearly sequenced six-phase pipeline with explicit validation checkpoints (confidence ≥ 80% drop, adversarial refutation, Phase 3 direction-error guard, harness permission gate); the validation is partly relay/non-gating rather than a hard fix-and-retry loop, a minor gap below a 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the body is well-organized into clear sections (Why, Caller Signature, Pipeline Overview, When to Use, Phase 0–4, Rules) with no need for external references; the >50-line length and the redundant Rules section keep it just short of a 5. | 4 / 5 |
Total | 15 / 20 Passed |