effort is accepted but ignored: every review agent runs at the session effort.
prflow_review.agent_overrides is an object. It accepts a default entry and these canonical agent keys:
prflow:checklist-generator.prflow:checklist-verifier.prflow:code-reviewer.prflow:silent-failure-hunter.prflow:comment-analyzer.prflow:type-design-analyzer.prflow:pr-test-analyzer.prflow:requesting-code-review.
devflow: spelling of each key remains accepted for existing configuration. Use prflow: for new entries. The checklist deduper no longer runs: an existing prflow:checklist-deduper entry is accepted and ignored.
A per-agent
model override is expressible only as one of the four accepted aliases (sonnet, opus, haiku, fable). A consumer whose model is addressed through a provider route sets it at the top-level claude_model rather than in an agent_overrides entry — that top-level setting still takes the full or provider-routed identifier the route expects.
An agent-specific entry replaces the default entry for that agent; the default does not fill missing fields inside a specific entry. The default applies only when no specific entry exists.
Valid Override Example
Coverage Reviewer and Proportionate Verification
A fresh install ships the coverage reviewer (prflow:pr-test-analyzer) with "iterations": "first-only", so it reviews on the first fix-loop iteration and the standalone review but is dropped from later fix-loop iterations. An existing configuration keeps its own value; the shipped default reaches an existing repository only for this key if the key is absent, at the next re-scaffold.
Implementation and fix runs choose the smallest reliable verification for the changed behavior, respecting your repository’s testing requirements and agreed criteria. Existing coverage or direct checks can suffice; permanent tests are added for consequential behavior that needs recurring protection. Test-first remains preferred for reproducible bugs. The coverage reviewer assesses meaningful gaps and accepts coverage at another level instead of requiring a test per changed function. Test Plans report actual checks and limitations without requiring test-authoring waiver declarations; historical decisions remain intact.