Code review
Turn on review with one organization-wide switch and every pull request gets a review of its new commits, posted as inline comments. Add a pipeline file to scope which pull requests are reviewed, write your own reviewers with their own prompts and models, and cap what a review can spend.
Each push gets a review of the commits since the last one, never the whole pull request again, and it never re-comments a line it already covered. Comments anchor to the reviewed commit, so GitHub collapses them as outdated when a later push changes those lines.
Only the commits since the last review
Each reviewer runs in its own sandbox with the repository at the reviewed commit, so it judges a change against the surrounding code rather than the diff alone. Findings post as one review, highest severity first.
# reviewing api-repo#512, push 2
$ pytest -k trade
14 passed
$ git diff HEAD~2 -- src/trade_engine.py
reads the actual change, runs the actual suite, then comments
Judged against the surrounding code, not the diff alone
A pipeline file in the repo declares reviewers with their own prompts, models, and path filters, such as a migration-safety specialist that only runs when a migration changes. Reviewers run in parallel, and a budget caps what one run can spend.
ellipsis: version: v1 kind: code_review name: Code review description: Review the new commits on every pull requestpull_requests: repositories: [web-repo, api-repo] for: users: true bots: falsereview: - name: correctness harness: type: claude_code model: claude-haiku-4-5-20251001 instructions: | Flag correctness bugs, unhandled edge cases, and breaking changes. Suggest the fix on the exact line.budget: run: 10.00Your prompts and your models, committed to the repo