Skip to content

Harness: isolated-review

Read-only reviewer (Bugbot / security-review shape). No writes.

When

A diff or tree needs a second pair of eyes without the reviewer "helping" by editing.

When not

You want the same agent to implement the fix — that is bounded-solo after review.

Topology

  1. Give the reviewer a path or diff and a question (correctness, security, completeness).
  2. Reviewer reads only. Output: findings with file:line, severity, and a recommended next step.
  3. Human (or a separate bounded-solo run) applies fixes.

Data class / OmniRoute

Same privacy floor as routing policy. Do not paste private_sensitive hunks into a cloud reviewer.

Invocation

Use the bugbot or security-review subagent when those match; otherwise a read-only chat with this page as the contract.