WORKFLOW · PR REVIEW BOT
Mention Reviewer.
Get the review back.
You are in a thread about PR #912. Type @bot/Reviewer and the review moves to Reviewer's own thread, on Reviewer's engine and standing rules. The parent shows a receipt, then the findings, and links to the full trace.
@bot/Reviewer review PR #912 for security and logic before we merge.
- Handoff receipt
- Two findings with lines and fixes
- Reviewer's delegated thread
UseAgentExample workflow@bot/Reviewer review PR #912 for security and logic before we merge.
Handoff receipt in the parent
Created: handed to Reviewer, thread here. The receipt names the delegated thread and the link opens it.
Reviewer opened the PR in its own thread
Fetched the diff on its own engine with its standing rules in front: security first, cite the line, never approve.
Security finding
Export query does not filter by org_id, so every org's rows come back. Flagged at handlers/export.ts:156 with a suggested fix.
Logic review
CSV writer passes user_email through unescaped. Second finding, with the line and a one-line fix.
Reported back to the parent
Reviewer's summary lands in the asking thread: two findings and the link to its full trace. The parent reads it and continues.
TOOLS IT REACHES
THE RESULT
Two findings back in the parent thread with lines and fixes. The full review lives in Reviewer's thread, linked from the receipt.
Questions, answered.
What is in the receipt?
One of three outcomes. Created: a new delegated thread, with the link. Sent: Reviewer already had a thread under this parent, so your message became its next turn. Refused: with the reason (itself, a cycle, the depth limit, or a cap) and when to retry.
Can Reviewer approve or merge?
No. Its standing rules say never approve, and GitHub writes go through approval gates anyway. It reports findings. A person decides.
Can an agent mention Reviewer mid-run?
Yes. An agent working in a thread can call the bot_handoff tool and gets the same receipt. The same loop guards and caps apply.
Why a separate thread instead of replying inline?
Reviewer keeps its own engine, rules and context. The parent stays readable, reports 'handed to Reviewer, thread here', and reads the result. Neither bot speaks as the other.
Start with one task.
See what you can hand off.
Explore a completed run, or join the early-access list to hear about getting your team started.