Code review

The review window, Review Pal, is where you read pull requests, have an agent review them and submit your review to GitHub.

The review window

Open a pull request

  • From the palette: ↵ to view a pull request, ⌘ ↵ to review it.
  • From the review window: paste a URL (https://github.com/owner/repo/pull/123) or owner/repo#123 in Paste PR URL. ↵ starts a review, the arrow button lets you View, Review or Review with template.
  • From the menu bar: Reviews.
  • From a review request notification.

Every pull request you open stays in the Reviews list on the left, with its status.

Toggle a filter next to Reviews to show only part of the list, or toggle it off to show everything:

  • To review: still needs your review and nothing blocks it.
  • Not ready: a draft, failing checks or merge conflicts.

Pull requests approved on GitHub, merged, closed, or that you reviewed with no new commits since are in neither. Statuses refresh every 5 minutes.

AI reviews

Git Pal clones the repository, checks out the pull request in its own worktree and asks your agent to review it. The agent gets the description and the existing discussion, so it doesn't repeat what's already been said.

Pick the agent, called the harness, and its model in Settings > General. Agents only read files and run git, they can't change your code or talk to GitHub.

While it runs, the button reads Reviewing with Claude Code. Click Cancel to stop it. Hover the harness logo next to the status to see who reviewed, with which model and template, and when.

Templates

A template holds the instructions the agent follows. Without one, the built-in instructions focus on bugs, security, performance and maintainability.

The template picker next to Review

Click Manage templates… at the bottom of the reviews list to create one:

FieldPurpose
NameShown in the template picker
InstructionsWhat to look for. The output format and the discussion are added for you
Risk guidelinesRules for the risk of merging, e.g. "migrations are always high"
SkillsInstalled agent skills the review must use
When to useA regex on owner/repo, e.g. ^acme/
Default templateUsed when no matcher accepts the repository
Auto-reviewReviews pull requests requesting you, or your team, as code owner
Skip approvedDoesn't auto-review pull requests whose required reviews are already met, on by default
Claim for teamAssigns you when auto-reviewing, so teammates in the requested code owner team skip it. The author is ignored, and you're unassigned if the review fails or is cancelled. Off by default
Skip labelsLabels keeping a pull request from being auto-reviewed, do not merge and do not review by default. Case, spaces, dashes and underscores are ignored
Auto-approveApproves clean reviews without asking
Max riskHighest risk auto-approved: minimal (default), low or medium
Require green CIAuto-approves only once CI checks pass

Drag templates to reorder them. Auto picks the template used last time on that pull request, else the first one whose matcher accepts the repository, else the default one, else the built-in instructions.

Risk

The agent rates the risk of merging the whole pull request, shown as a gauge next to the status. Hover it for the Merge Risk Assessment: the reasons, how sure the agent is, a rating per factor (blast radius, sensitive areas, test gaps, rollback difficulty) and the files driving the risk. Click a file to open it.

The merge risk assessment

RiskMeaning
MinimalNo runtime behavior change, e.g. documentation, comments or tests only
LowSmall and isolated change, easy to revert
MediumChanges existing behavior or shared code
HighMigrations, security, public APIs, infrastructure or large refactors

Each factor uses the same levels, high always being the risky end:

FactorHigh means
Blast radiusThe change can affect much of the product and its users
Sensitive areasIt touches security, authentication, payments, data or infrastructure
Test gapsTests barely cover the change
Rollback difficultyHard to undo, e.g. migrations or published APIs

Factors explain the level, auto-approve only looks at the level.

A template's Risk guidelines adjust both, they take precedence over the levels above. For example:

- Files under `migrations/` are always high risk, rollback difficulty is high.
- `billing/` is a sensitive area.
- Changes to `src/legacy/` have test gaps, it has no tests.
- Copy changes in `locales/` are minimal risk.

A pull request adding a migration is then rated high with a high rollback difficulty, even if it's small. A translation fix stays minimal, so it can be auto-approved.

Auto-approve

With Auto-approve on, a review is approved when it ends if:

  • the risk is at most the template's Max risk, and the agent isn't unsure about it,
  • there are no error or warning comments, nor notes waiting to be submitted,
  • no commits were pushed during the review,
  • CI checks passed, unless Require green CI is off.

Otherwise, hover the risk to see why it wasn't approved. With Auto-review on and review request notifications enabled, code owner review requests are reviewed as they arrive, so they can be approved without you. Drafts, approved pull requests and those with a skip label wait until marked ready, no longer approved or unlabeled.

New commits

When the pull request changes after a review, a banner offers to Review new commits, keeping existing comments, or to Re-review everything. To start over at any time, use Review again in the ⋯ menu. AI comments you haven't posted are replaced, your notes are kept.

Comments

AI comments are tagged Error, Warning or Info, and appear under the lines they're about. Nothing is posted until you say so:

  • Add to review queues the comment. It then reads In review, hover it to Remove it.
  • The pencil edits it.
  • Ask AI sends it to the agent chat.

Your notes

Click a line number to comment on it, drag or ⇧-click to comment on several lines, or use the file header's button to comment on the whole file. Type @ to mention someone and : for emoji. ⌘ ↵ saves the note.

Notes and queued AI comments are posted with your next review.

GitHub threads

Existing review threads show in the diff. Open them on GitHub, ask the agent about them, or edit and delete your own.

Submit

The submit review popover

Submit review shows how many comments are pending. Write an optional summary and pick:

  • Comment: feedback without explicit approval.
  • Approve: approve the changes.
  • Request changes: feedback that must be addressed before merging.

Status

StatusMeaning
TodoNot reviewed yet
In progressAn agent is reviewing, or there's something to submit
ApprovedYou approved, or, on the open pull request, its required reviews are met on GitHub
Change requestedYou, or a reviewer on GitHub for the open pull request, requested changes
Feedback submittedYou commented
Merged, ClosedMerged or closed on GitHub before you submitted a review

Your reviews count whether submitted from Git Pal or on GitHub. A new commit or a pending comment puts a submitted pull request back in progress.

Files and diff

  • The file tree shows each file's changes and comments, colored by severity. Switch between tree and list, search with ⇧ ⌘ F, filter by status (Modified, Deleted, New file, Renamed), and show Only files owned by me when the repository has a CODEOWNERS file.
  • Tick Viewed to dim a file and jump to the next one. A viewed file that changes is unticked.
  • Switch between split and unified diffs with ⌘ S. Narrow windows switch to unified on their own.
  • Expand hidden lines around each hunk, and find in the file with ⌘ F.

Conversation and summary

The header buttons open the pull request's Conversation (description, reviews and comments) and the agent's Review summary. A dot marks a summary you haven't read.

Open in your editor

The ⋯ menu opens the pull request's worktree in your editor, or copies its path. Git Pal finds VS Code, Cursor, Windsurf, Zed, Sublime Text and the JetBrains IDEs.

Agent chat

The agent chat next to the diff

Press ⌘ I to chat with the agent about the pull request. It runs in the pull request's worktree and sees the file you're on. Type @ to add files or comments as context. Chats are saved per pull request, find older ones in History.

Shortcuts

Windows and Linux use Ctrl where macOS uses ⌘. Hold ⌘ to see shortcut hints on buttons, press ⌘ / to list them.

Shortcut hints shown while holding ⌘

ActionmacOS
Hide or show reviews⌘ B
Previous file⌘ [
Next file⌘ ]
Check for updates⌘ R
Split or unified view⌘ S
Submit review⇧ ⌘ ↵
Open on GitHub⌘ O
Agent⌘ I
Keyboard shortcuts⌘ /
Find in file⌘ F
Search files⇧ ⌘ F
Paste pull request URL⌘ N