Skip to content
Guided Review
Documentation

Your first review

From a normal GitHub PR page to a structured walkthrough in a few clicks. This page is the Chrome extension path. For a local branch, commit, or working tree, use the CLI instead. If the extension isn’t installed yet, start with Chrome Extension.

Open a pull request

Navigate to any pull request on github.com (Conversation, Files changed, or Commits). The content script is injected on https://github.com/* so SPA navigation from the PR list still shows the button when you land on a PR.

No button? See Troubleshooting. Some PR sub-pages (for example conflict resolution) are intentionally ignored — same troubleshooting page.

Start Guided Review

You can open the overlay any of these ways:

  1. Click Start Guided Review on the PR page.
  2. Click the Guided Review toolbar icon while a PR tab is active (pin it from Chrome’s puzzle-piece menu so it stays visible — Chrome Extension).
  3. Optionally enable Automatically Open on Files Changed in Options so the review starts (or resumes) when you open that tab (classic /files or the newer /changes path). Off by default.

Then:

  1. The overlay opens in a Shadow DOM host so its styles don’t fight GitHub’s CSS.
  2. The extension fetches the PR diff.
  3. With a provider configured, it streams an ordered walkthrough from your model. Review units appear progressively as each chunk finishes; the final walkthrough is what you step through.
  4. Without a provider key, you still get a walkthrough: one unit per changed file, in diff order. The context panel prompts you to connect Claude, OpenAI, or Grok so related changes can be clustered and summarized. See How a review plan works → Without a provider.

Connection failures after a key is set: Troubleshooting.

Follow the Walkthrough

The overlay shows each step in order: a synthetic PR description first, then the review units. UI map (sidebar, context, header): Reading the overlay. How units are built and validated: How a review plan works.

For each unit you can:

  • Read the unit’s title and guidance (take summaries with a grain of salt — see the FAQ)
  • See the linked hunks from the real diff (default split view; switch with v u / v s, or the toolbar — choice is remembered). Images and binary files use a preview or empty state instead of a line patch.
  • Move next / previous with the footer or keyboard shortcuts

With AI, the model chooses order and commentary; it does not supply the code lines you see. Hunk ids that don’t match the parsed diff are dropped. Without AI, order is file order and commentary is empty until you connect a provider.

Search the diff

Press ⌘/Ctrl + F to search file paths and code across the whole PR diff. Pick a result to jump to the unit that owns that match. Full behavior: Keyboard shortcuts → Diff search.

Leave comments and submit

As you walk:

  1. Press c to enter comment mode, select lines, and draft line comments. Drafts stay local until you submit (privacy).
  2. When you’re ready, press ⌘/Ctrl + Enter (or use Submit Review) to choose Comment / Approve / Request Changes and send the review.

Submit needs GitHub connected. Following the walkthrough and drafting do not. Full shortcut list: Keyboard shortcuts.

Resume later

Sessions (diff, plan, PR context, current step, drafts) are stored in chrome.storage.session, keyed by owner/repo#number — not the full URL — so you can switch between Conversation and Files changed tabs and resume the same plan until the browser session ends. Limits and clears: Troubleshooting.

If something fails mid-flight, see Troubleshooting.

Next. Reading the overlay · CLI · How a review plan works · Leave line comments

← PreviousConnect GitHubNext →Reading the overlay