Content
63%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.
The body is a solid, largely executable workflow document with strong validation checkpoints and concrete commands. Its weaknesses are heavy repetition of policy conditions across sections and a monolithic single-file layout that inlines template/example material that belongs in reference files.
Suggestions
State each policy condition (authorization contract, size:exception authority) once in Critical Rules and reference it elsewhere — e.g. replace repeated clauses in the checklist and Automated Checks table with "per Rule 3".
Move the full PR body schematic and the commit-message example set into a references/ file (e.g. references/pr-template.md, references/conventional-commits.md) and keep only the pattern plus one example inline.
Make step 3 of the Workflow concrete by naming the applicable local checks (go test ./..., go run ./internal/gofmtcheck) instead of "run applicable local checks".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body teaches nothing Claude already knows and its tables earn their place, but authorization boilerplate ("a current direct human instruction binding the exact target/action") and size:exception authority conditions are restated verbatim 4-6 times across Critical Rules, Workflow, the checklist, and the Automated Checks table. | 3 / 5 |
Actionability | Concrete executable commands (gh issue view, go test ./..., gh pr checks), exact regex patterns, a full PR-body schematic, and a type-to-label mapping table give mostly copy-paste-ready guidance; minor gaps like "run applicable local checks" and the deliberately non-executable PR-creation step keep it below a 5. | 4 / 5 |
Workflow Clarity | The five-step workflow is clearly sequenced with explicit validation checkpoints (verify status:approved, resolve the default branch rather than assuming main, mark checkboxes only after observed readback, report baseline unverified). Step 3's "run applicable local checks" is vague and error-recovery guidance is thin, so it does not reach a 5. | 4 / 5 |
Progressive Disclosure | The single-file body is well-organized with headers and tables, but ~250 lines inline the full PR-body template and twelve commit-message examples — content that clearly belongs in reference files; no bundle structure exists to offload it. | 3 / 5 |
Total | 14 / 20 Passed |