Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
PR Review
With PRs named, check each one. With none, check every open non-draft PR in the current repository that has no recommend-* label, one subagent per PR.
Check the title, description, and tests against the linked issue and the code at the head commit; they are claims.
Answer four questions in order, each with one line of evidence:
- Meaningful: is the problem real and still present on the base branch?
- Worth adding: does the value justify the scope and ongoing maintenance?
- Correct: does it solve the problem without breaking a caller or edge case?
- Minimal: is every changed line needed, with nothing that existing code already does?
Take the first failure's verdict:
| Fails | Verdict |
|---|---|
| Meaningful, or Worth adding for a technical reason | recommend-close |
| Worth adding as a product or scope call | recommend-triage |
| Correct or Minimal | recommend-revise |
| Nothing | recommend-merge |
Report to the caller the verdict, the four answers, and for revise the specific changes needed. The caller decides what reaches the PR.
