Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with concrete commands, regexes, and validation checkpoints supporting clear end-to-end workflows. Its main weakness is redundancy — several repo-specific facts are restated across multiple sections — and a monolithic inline structure with no bundle files to offload detail.
Suggestions
Consolidate repeated facts: state the GraphQL 403 'AddLabelsToLabelable' error, the cross-fork base-ref limitation, and the pre-existing test-failure list once in their canonical section and reference them elsewhere rather than re-explaining in the scope table, verification protocol, and anti-patterns.
Move the anti-patterns table and/or the 'Standard honest-rewrite pattern' into a reference file under references/ to reduce inline length and improve progressive disclosure.
Trim the overlap between 'Hard rules' and the workflow sections, which restate the same Closes-vs-Refs, single-scope-title, and 400-line-budget constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and avoids explaining general concepts Claude already knows, but repeats the same repo-specific facts multiple times — the GraphQL 403 'AddLabelsToLabelable' error, the cross-fork base-ref limitation, and the pre-existing test failures each appear in 3+ sections (hard rules, scope table, verification protocol, anti-patterns), which could be consolidated. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready guidance: concrete `gh pr view --json ...` commands, exact branch-name and PR-title regexes, specific file paths, and a literal PR body section template with emoji headers — no vague direction. | 3 / 3 |
Workflow Clarity | Multi-step processes (Issue workflow, PR workflow, Verification protocol) are clearly sequenced with explicit validation checkpoints — API cross-checks, `git stash` baseline, `gh pr checks --json`, and round-trip body verification — plus a pre-PR self-audit checklist and feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Sections are well-organized and the 'Source of truth' and 'References' tables point one level deep to real repo files (CONTRIBUTING.md, skills/*/SKILL.md), but no bundle files exist and the ~290-line body is largely monolithic inline content (e.g. the anti-patterns table and standard honest-rewrite pattern) that could be split into reference files. | 2 / 3 |
Total | 10 / 12 Passed |