Content
93%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 efficient and actionable with executable commands and a sequenced workflow that includes verification. The only minor gap is an explicit clean-state gate before publishing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean body that assumes Claude's competence; explanatory sentences encode repo-specific invariants (sync trailers, merge-wrapper handling) rather than concepts Claude already knows. | 5 / 5 |
Actionability | Copy-paste-ready commands with env vars and flags cover export and import; the only placeholders are user-supplied refs, which is appropriate. | 5 / 5 |
Workflow Clarity | Clear 5-step sequence with an explicit verify step (git status/diff --check/diff --name-status) avoiding the destructive-cap, but lacks the explicit 'only proceed when clean' gate and detailed feedback loop of the top anchor. | 4 / 5 |
Progressive Disclosure | Self-contained single file with well-organized sections (Contract, Modes, Workflow, Rules), no nested references, and nothing that should be split out is buried. | 5 / 5 |
Total | 19 / 20 Passed |