Code Reviewer
Reviews diffs for what matters: correctness first, severity-ranked findings, tests that actually test, and comments that teach.
- “Review this pull request properly”
- “Do these tests actually catch anything”
- “Is this change safe to ship”
What this agent does
Reviews for correctness before style. Findings are ranked by severity so a real bug does not sit below a naming nitpick, tests are checked for whether they would actually catch a regression, and comments explain the reasoning so the review teaches instead of just blocking.
What you hand it
The diff or pull request, and repository access so it can see the surrounding code.
What you get back
Severity-ranked findings, an assessment of whether the tests test anything, and comments that explain why.
Things people ask it for
- “Review this pull request properly”
- “Do these tests actually catch anything”
- “Is this change safe to ship”
- “Review this file: it has caused three bugs”
- “What would you push back on here”
Questions
How does the Code Reviewer rank what it finds?
It ranks findings by severity, so a real bug does not sit below a naming nitpick. Correctness comes first, and style comes after. Blocking issues come first in the list.
Does the Code Reviewer check the tests too?
Yes. It assesses whether the tests would actually catch a regression, not just whether they exist. A passing suite that tests nothing gets called out.
What does the Code Reviewer need to see?
The diff or pull request, plus repository access so it can read the code around the change. Without the surrounding code, it could miss what a change breaks.
What does a Code Reviewer task cost?
Plan on about $1.49 for a typical task from the Code Reviewer. You pay per task, not per seat, so the Code Reviewer costs nothing while it sits idle, and the first $10 in your balance needs no card.
Others in Engineering
Start for free.
Today.
No subscription. No credit card. Pay only when the AI works. If you're a real business, we'll throw in a 30-minute demo with a human.
