Skip to content
Guided Review
Documentation

Approve or request changes on a GitHub pull request

Use Approve when the change is ready, Request Changes when a correction is needed before merge, and Comment for feedback without either decision. You can submit these reviews on GitHub or through Guided Review. Approval records a review decision; it does not merge the PR.

In Guided Review, post drafted line comments and an overall decision to the pull request through the GitHub API — without leaving Guided Review. This is a Chrome extension feature; the CLI keeps notes local and offers Generate Prompt instead.

This path requires GitHub connected. Generating and walking a plan does not — see Your first review and the FAQ.

The model never submits for you (FAQ).

Approve or request changes on GitHub

Without the extension, open the PR's Files changed tab, inspect the diff, and choose Review changes. Write your summary, select Comment, Approve, or Request changes, then choose Submit review. These are the steps documented by GitHub.

If you drafted comments inside Guided Review, submit them from the overlay using the steps below. Local extension drafts are not GitHub's pending review comments.

Before you submit

  1. Finish walking the plan and draft any line comments you want included.
  2. Confirm you’re signed into the extension with an account that can review that PR (collaborator / required reviewers, org SSO if applicable).
  3. Remember: you still have the final say. The model ordered the walkthrough; the approve / request-changes decision is yours.

Open Submit Review

  • Press ⌘/Ctrl + Enter from navigate or comment mode (not while typing in the composer — there it saves the draft). See Keyboard shortcuts.
  • Or use the Submit Review control in Guided Review.

If GitHub isn’t connected, the Connect GitHub modal opens first. Complete device OAuth, then submit again.

Choose a review type

The dialog mirrors GitHub’s review events:

TypeUse it whenSummary in Guided Review
CommentYou have a question or nonblocking feedback without an approval decision.Required.
ApproveYou have verified the change and have no outstanding merge-blocking concerns.Optional.
Request ChangesA specific correction is needed before merge.Required.

For example, if a retry change ignores the server's delay, request changes with the input, observed behavior, and expected result: “A 429 with Retry-After: 30 retries immediately. Please preserve the delay and add a test for that response.” If you only suggest renaming a helper, label it as optional and use Comment if you are not making an approval decision.

After the author fixes the retry path, inspect the updated code and test before approving. Explain what you checked in the summary. The code review checklist gives you a compact final pass.

Use ↑ / ↓ to highlight a type and Enter to continue, or click.

Submit Review dialog offering Comment, Approve, and Request Changes.

Captured with the sample PR. The live preview simulates submission; an installed extension posts when you confirm.

Why a pull request is still blocked after review

GitHub's review rules distinguish a review from permission to merge:

  • Request Changes blocks merging only when repository rules enforce it for the reviewer's permission level.
  • An approval can still leave required checks or other review requirements unsatisfied.
  • New commits can dismiss an approval when stale-review dismissal is enabled.
  • You cannot approve your own PR.

If a corrected PR still shows changes requested, the original reviewer should re-review and approve it. Resolving a conversation alone is not an approval. Check the PR's merge requirements on GitHub before assuming the review has cleared the restriction.

Summary and send

  1. Write a top-level review summary for Comment or Request Changes; it is optional for Approve.
  2. Press ⌘/Ctrl + Enter or click submit.
  3. The extension posts the review and all current drafts as line comments via your stored token. What leaves the browser: Privacy & data.

Request Changes selected with a review summary asking to preserve Retry-After and test the delay-cap boundary, ready for confirmation.

Errors from GitHub (permissions, expired token, stale line anchors, SSO) surface in the modal with a short next step — see Troubleshooting → GitHub connect and submit and Private repos and SSO.

After submit

On success:

  1. Drafts for that submission are cleared.
  2. A short confirmation appears; Enter or Esc dismisses it and closes the guided review (shortcuts).
  3. You’re returned toward the PR conversation view so you can see the review on GitHub.

You can start Guided Review again later if the PR gains new commits; that builds a new plan for the current diff. Session storage limits: Troubleshooting.

Note

Note. Guided Review never auto-approves. Submit only runs when you confirm the dialog.

Next. Leave line comments · Connect GitHub · Troubleshooting