Show HN: GuidedReview – Review AI-generated code before you sign your name to it GuidedReview, a free open-source tool from developer Nshntarora, turns GitHub pull requests and local git changes into an ordered walkthrough of review units, clustering related code hunks with AI commentary so developers can read diffs with intent. The tool, available as a Chrome extension and CLI via `npx @guided-review/cli`, requires users to bring their own LLM API key and has no product backend, with the code always sourced from the real diff for the developer to read and decide. GuidedReview addresses the difficulty of reviewing large AI-generated code changes by providing structure while emphasizing that automated review agents lack taste and cannot replace human judgment. Guided Review turns GitHub pull requests and local git changes into an ordered walkthrough of review units so you can read the change with intent instead of reconstructing it from an alphabetical file list. 1. Run npx @guided-review/cli in your project directory or click on Start Guided Review on a GitHub PR if you're using the Chrome Extension 2. When you ask for AI structure, your LLM clusters related hunks and adds short commentary — schema, then logic, then call-sites, then tests. 3. Follow the walkthrough keyboard-first. The code always comes from the real diff; you still read it and decide . Free, open source, bring your own LLM key. Guided Review has no product backend: the extension and CLI talk directly to your AI provider, and the extension talks to GitHub for PRs. - Chrome extension — Chrome Web Store https://chromewebstore.google.com/detail/pdnnimoajmnjpccboemeomoeomancodd , or build from source below - CLI — npx @guided-review/cli npm https://www.npmjs.com/package/@guided-review/cli Site and docs: guidedreview.dev https://guidedreview.dev · docs https://guidedreview.dev/docs . Automated review agents help find bugs and edge cases you missed — useful — but they are not a replacement for you. They lack taste: product context, people, when an abstraction is unnecessary, when to break the rules. Even with AI today, nothing beats reading the code. GitHub still hands you every changed file in alphabetical order; a raw git diff is no better. That was awkward for human-written diffs; for large AI-shaped changes it is actively hostile. Guided Review uses AI only where it helps: clustering related hunks into a walkable order and adding short summaries you can take or ignore. The Chrome extension does this on GitHub PRs. This CLI does the same for local work — before you open the PR, or when there is no PR at all. From the store: install from the Chrome Web Store https://chromewebstore.google.com/detail/pdnnimoajmnjpccboemeomoeomancodd , open Options → add an LLM API key → open a GitHub PR → Start Guided Review . From source — requires Node.js ≥ 22, pnpm ≥ 11, and Chrome : 1. Install dependencies from the monorepo root: pnpm install 1. Build the extension: pnpm build:extension 1. Load it in Chrome: - Open chrome://extensions - Enable Developer mode - Load unpacked → select apps/extension/dist never a root-level dist/ 2. Open 3. Open Options → add an LLM API key → open a GitHub PR → Start Guided Review Requires Node.js ≥ 22. No clone needed: npx @guided-review/cli The CLI starts a local server on 127.0.0.1 , opens a browser UI, and walks the current branch versus its base, uncommitted work, or a single commit. It starts file-by-file and does not call an LLM until you click Structure With AI . npx @guided-review/cli --base main --no-open npx @guided-review/cli --staged --agent claude-code The binary is guidedreview . Full detail: CLI https://guidedreview.dev/docs/cli · apps/cli/README.md /nshntarora/guidedreview/blob/main/apps/cli/README.md . From this repo after pnpm install : pnpm build:cli pnpm review pnpm review -- --base main --no-open For day-to-day work with HMR: pnpm dev extension Vite / crx on port 5173 pnpm dev:cli CLI UI + server pnpm dev:web marketing site → http://localhost:3000 After extension code changes, rebuild if needed pnpm build:extension , Reload the extension card in chrome://extensions , and refresh the PR tab. Chrome serves whatever is currently in dist/ — a running dev server alone does not replace that reload. More detail: apps/extension/README.md /nshntarora/guidedreview/blob/main/apps/extension/README.md · apps/cli/README.md /nshntarora/guidedreview/blob/main/apps/cli/README.md · apps/web/README.md /nshntarora/guidedreview/blob/main/apps/web/README.md . pnpm build:extension typecheck + Vite → apps/extension/dist + zip pnpm build:cli CLI binary + UI → apps/cli/dist pnpm build every workspace package with a build script extension, site, CLI pnpm build:web Next.js static export → apps/web/out From the monorepo root: pnpm test unit tests extension + UI pnpm test:e2e:install Chromium for extension e2e once pnpm test:e2e extension Playwright e2e builds first pnpm test:e2e:web marketing site e2e builds first pnpm test:e2e:cli CLI Playwright e2e builds first Also available: pnpm typecheck , pnpm lint , pnpm format . Workspace-scoped runs use pnpm --filter @guided-review/