Genie Review

Inline pull-request review that tries to prove itself wrong before it speaks. Every finding ships with a proof packet. 50 reviews per month free.

What it does

On every pull request, Genie posts a walkthrough summary and inline comments. Before a finding is posted, a second self-verification pass attempts to falsify it — findings that don't survive are dropped. What reaches your PR comes with a proof packet: the evidence, the reasoning, and the exact lines that justify the claim.

Why it's different

Proof-backed, not guess-backed. If Genie claims a bug, it attempted to falsify that claim first. Noise is the #1 reason teams turn AI review off — Genie optimizes signal over recall.
Never breaks your code. Committable suggestions pass a sanitizer; when the model isn't confident, the suggestion is omitted rather than risked.
Dedup across runs. Re-triggering a review shows progressively less noise, not the same wall of text again.
The walkthrough is the product. The summary is the most-read artifact in code review — it's treated as P0, not an afterthought.
Your data never reaches a third party. Your code is processed only by Genie, a US company, on infrastructure we run — never sold, never used to train a model, never handed to another vendor. See Genie Fleet.

Proof packets

A proof packet is the audit trail behind a finding: what Genie believed, the evidence it gathered, the falsification it attempted, and the verdict. It's why a Genie comment is something you can act on rather than something you have to second-guess.

Proof PacketVERIFIED

Session recording

0:42

Screenshots

3 captures

App map

11 routes · 1 orphan

Console + network log

0 errors

Open a live proof packet →

Each tile is an artifact you can open — the session recording, the before/after screenshots, the route-coverage map, and the console + network log. Click through any of them on the demo proof packet.

Reviews run on the same persona-routed local inference as the rest of the platform. A review is a unit of work on the fleet, billed against your monthly allowance.

Triggering a review

Automatic on every pull request once the GitHub App is installed.
On demand by commenting /review on a PR — re-runs dedup against prior findings.
Tune scope and severity from your dashboard.

When the `Genie Proof` check skips

Alongside the review, a separate Genie Proof check renders the routes your PR affects against the preview deploy and compares before/after. It runs when the diff touches a page or anything a page transitively imports — components, hooks, state repositories, utilities. It skips when the diff only changes things no shipped page depends on: standalone API routes, worker code, scripts, fixtures, type-only declarations.

If you expected proof to run and it skipped, the usual causes:

The page hasn't been scanned yet.Proof works off a route graph (the "app map") refreshed on every push to your default branch. A brand-new branch with no prior main push won't have a map to consult. Merge once tomain, then re-open the PR.
The file you edited isn't imported by any page.Worker-only code, CLI tools, infra scripts, and pure types never trigger proof — there's no visual surface to verify.
The PR is a draft. Proof respects the same gate your review settings use.

Proof is capped at 5 routes per PR. A refactor that touches a dependency 30 pages share will queue proof for the first 5 routes, not 30 — same diff, bounded cost.

Get started

Install the GitHub App, open a pull request, and Genie comments within minutes. See it in action on the developers page. Review is one click on top of Genie Rollup — same install, same bill.