Content
88%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 content is an efficient, actionable PR-management workflow with strong sequencing and validation checkpoints, largely free of padding. Its only weak spots are unspecific placeholders in the gh API examples and a lack of any progressive file split.
Suggestions
Replace abstract placeholders (<COMMENT_ID>, <PRRT_...>, [commit], [description]) with concrete captured-variable examples or a short note showing how to extract the real value from the prior command's JSON/JQ output.
Add a one-line note in Step 4 on how to obtain the GraphQL threadId (e.g., the id field returned by the reviewThreads query in Step 1) so the resolve mutation is fully executable.
Consider moving the Special Operations rebase/recreate/delete recipes into a referenced file or a clearly marked appendix to keep the main workflow path uncluttered.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — almost entirely executable commands and terse decision criteria — with no padding explaining what a PR or gh is; even rationale is compressed to one-liners like 'Why: Unresolved threads block merging even after approval.' | 5 / 5 |
Actionability | Concrete, copy-paste-ready gh commands and GraphQL queries cover the common cases, but placeholders such as <COMMENT_ID>, <PRRT_...>, [commit], and [description] require manual substitution, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear 6-step sequence with an explicit feedback loop ('Repeat Steps 1–5 until: All CI checks green, All review threads resolved, No new blocking comments') and validation via re-checking CI; the 3-attempt cap and 'NEVER merge automatically' rule add safety for destructive/batch operations. | 5 / 5 |
Progressive Disclosure | Well-organized into clearly headed sections (Step 1–6, Special Operations, Rules) in a single self-contained file with no nested references; no bundle files are needed or present, though at over 50 lines it is not a minimal simple skill. | 4 / 5 |
Total | 18 / 20 Passed |