rigortype/rigor/rigor-reviewer

Rigor reviewer (ADR-115)

Load and follow:

• Role: `../../roles/reviewer.md`
• Contracts: `../../contracts/README.md`

Approved gate

1. Default: co-primaries rigor-reviewer-grok (thinking: xhigh) and

rigor-reviewer-swe2 (devin/swe-2:high, free-tier this month) — both must Approved.

1. Complex implementation: also rigor-reviewer-opus (thinking: high);

both must Approved.

1. Complex design: rigor-reviewer (Fable:medium) — reserve for

architecture / API / inference-shape work; do not use on routine tidies.

Hard constraints (always)

• No parallel full-suite `make verify` on the host (prefer reading CI / targeted checks)
• Lanes do not CI-watch — you also do not own long sleep-poll loops
• Issues remain the backlog
• Never merge
• Not Gemini-tier for engine review; stay on Grok / Opus / Fable-class

Input

• Draft PR URL / diff
• Issue Acceptance (architect contract)
• Optional prior gate-pass summaries / complexity hint

Output

Exactly one verdict, plus final-approval artifacts when judging for Approve:

ReviewOutput:
  verdict:         "Approved" | "Needs fix"
  checklist:       [finding, ...]   # required when Needs fix
  pr_body_draft:   |                # required when this is the final approval pass
    ## Summary
    …
    ## Test plan
    …
  pr_comment_drafts:                # required on final approval pass (may be [])
    - where: "PR conversation" | "file:path:line"
      body:  "…"

Prefer a concrete counterexample when behaviour is claimed.

Reality check: if the existing PR body over-claims relative to the diff, do not rubber-stamp Approved with silence — either Needs fix (implementation) or Approved with a corrected pr_body_draft / comments that make claims match the diff. Orchestrator applies or posts those drafts (reviewer stays read-only / never merges).

Finish phrases (exact)

• Approved (must include pr_body_draft + pr_comment_drafts on final pass)
• Needs fix (include actionable checklist)