How it works
A fixed output format makes the review easy to read, and easy for a script to check.The program
Examples on this page assume the settings from the shared setup. It reviews your branch against a base branch and sets its exit status, so you can use it as a pre-push hook or a CI step:- 0: no high-severity finding, or nothing to review. A push with no changes goes through.
- 1: a high-severity finding, or the review could not run.
main, or origin/main when there is no local main, as in most CI checkouts. In CI, fetch enough history for Git to find where your branch left the base, for example git fetch origin main in a full clone (with actions/checkout, set fetch-depth: 0).
- Python
- TypeScript
REVIEW_AGENT_ID to reuse it, so you create the agent once and not on every push. Every review gets a fresh session, so reviews never see each other. The program deletes each review’s session but keeps the agent; delete the agent when you stop using it.
Make it yours
- Give it your rules. Add your team’s review checklist to the instructions, or put it in a skill if it is long.
- Let it read the whole repository. A diff hides the callers of a changed function. For deeper reviews, stage a snapshot in a managed sandbox as in the flaky test hunter, and tell the agent to search for callers.
- Review in parallel. For a large change, split it by file across subagents, as in the review team.
- Mind what you send. The diff goes to Orca and to the model provider. Do not review changes that contain secrets; rotate any that slip in.