Best for
- Solo developers with nobody to review their work
- Teams whose reviews have drifted into rubber-stamping
- Catching the bug before the customer does
What you give it
- A diff, a branch, or a set of changed files
- Your review standards, if you have them written down
What you get back
- Findings ranked blocker / should-fix / nitpick, each tied to a file and line
- The reasoning behind every finding — not just 'change this'
- An explicit verdict: safe to merge, or what must change first
How it works
- Reads the change AND the surrounding code it touches, not the diff alone.
- Checks correctness first: logic, edge cases, error paths, concurrency.
- Then security and data handling, then clarity and consistency with the codebase.
- Ranks findings by consequence, so a style remark never buries a bug.
- Gives a verdict with reasons — it never waves a change through by silence.
Example
You: Review the branch that adds bulk invoice export.
Result: One blocker (the date filter drops the last day of the range), two should-fixes (an unawaited promise, a missing permission check on the new endpoint), three nitpicks — each with file, line and reasoning, and a clear 'not yet' verdict.
Limits — please read
- It reviews what it can read; behaviour only visible at runtime needs tests too.
- It flags design concerns but will not redesign the change inside a review.
- Standards it is not told about are judged by common practice, and it says so.