Review AI-generated code before you sign your name to it
Follow each change across files with AI-organized review units. Read the real diff, leave feedback, and decide what ships — locally or on GitHub.
Free · Open source · Bring your own LLM key
Your provider: Anthropic · OpenAI · Grok
Local changes- View CLI docs →
npx @guided-review/cli GitHub pull requests
- Opens the Chrome Web Store
Try it out without installing anything
Play around with Guided Review before you decide to install
From diff to decision
Same code. A better order to read it.
Group related changes, read the diff, and leave your feedback. AI structures the review; you decide what ships.
- 01 / Group the change
Start with a plan.
Related implementation and tests become ordered review units, so you can follow a change across files.
Changed files
- README.md
- src/client.ts
- src/index.ts
+ 9 more files
Ordered review units
- 01Define the retry contract
- 02Decide which responses can be retried
- 03Schedule retries with jitter
- 04Make pending waits cancellable
- 05Connect retries to the public client
- 02 / Read the real diff
Read with context.
Read each unit alongside its summary. Inspect the original changed lines and make your own call.
Diff excerpt
const ceiling = Math.min(options.maxDelayMs, options.baseDelayMs * 2 ** attempt); const jitter = Math.floor(random() * ceiling); return Math.min(options.maxDelayMs, Math.max(jitter, retryAfter ?? 0));The code comes from your diff. AI supplies structure and commentary.
- 03 / Leave your feedback
You make the call.
Select the lines that need attention and leave a note. Your feedback stays attached to the code you read.
Selected lines · Your feedback
Please cover this edge case with a test before merging.
- Reviewing locally?
- Copy your notes as a coding-agent prompt.
- Reviewing on GitHub?
- Submit your feedback as a PR review.
- ←→ Navigate units
- c Comment on a line
- ⌘ / CtrlK Open actions
Install
Same review engine for local changes and GitHub pull requests.
CLI
When you're reviewing your own code.
Review a local branch, commit, or working tree in the browser — before you open a PR, or when there isn't one.
In your project directory, run:
npx @guided-review/cliThe server will start up. Requires Node.js 22+.
Full flags and scopes: CLI docs →

Chrome Extension
When you're reviewing pull requests on GitHub
Add Start Guided Review on GitHub pull requests — walk the same plan on the real PR diff.


Features
Built for humans who still have to read the code.
- navigation.keys
Read and navigate how you write
Guided Review is keyboard-first. Browse units, comment, and submit without leaving the keys — same muscle memory as writing code.
- summaries.ai
Summaries (because AI)
Get a 2 line overview of every change. Sometimes it's really helpful, sometimes it's not. Take it with a grain of salt.
Model companies apparently block your API keys if you do not implement summarization. Seriously.
- approved-tools.json
Tools corporate security has already approved
Bring the AI provider your company already approved — Claude, OpenAI, or Grok — and your own API key. Want to read the code that handles that key? It's open source (without VC funding), so you can read it, or fork it and point it somewhere else, or modify it for your own workflow.
Please check with your employer if they've policies about this. If you're a 2 person startup, you're (probably) fine.
- manual-review.diff
AI and IDE optional
Not every change needs a full AI-powered review. Sometimes you just need to read the diff. Open it in your browser and work through the changed files yourself — no API key, no AI generation, no full IDE to load into memory.
Browse the file list, search the diff, and leave line notes from the keyboard. Your mouse can sit this one out.
Local review → next iteration
Turn review notes into the next coding prompt.
Read the diff. Leave notes on the lines that need work. Generate Prompt bundles your feedback with file paths, line ranges, and selected code.
Copy it into Claude Code, Codex, or your coding agent. You choose what to send and when to run it.
How Generate Prompt works →Example prompt excerpt · from your note
src/retry/backoff.ts:11
Honor Retry-After when it exceeds the configured delay cap. Add a regression test for a long header value.
Built from your notes · Clipboard handoff · No extra LLM call
Your code never touches our infrastructure
The extension and CLI talk directly to your AI provider (and GitHub for PRs). We never see your diffs, your keys, or your code — because there's nothing on our end to see them with.

Get Guided Review
Run npx @guided-review/cli for local changes, or install the Chrome extension for GitHub PRs. Add an LLM API key, then follow the walkthrough — AI structures it, you decide.