Pull Request Reviews
Review GitHub pull requests inside Nimbalyst. Read the diff, run an AI review, open the branch in a worktree, then comment, approve, or merge.
Review GitHub pull requests without leaving Nimbalyst. Pull Request mode brings the conversation, changed files, commits, checks, tracker-based triage, and AI review workflow into one place.
See code review for how teams run AI-assisted reviews end to end.
Before You Begin
Pull Request mode is available when:
Developer Mode is enabled. See Turn on/off Developer Mode; the setting is under Settings, Advanced, Application Mode.
The project is a Git repository whose
originremote points at GitHub (GitHub Enterprise hosts work too).The GitHub CLI is installed and signed in with
gh auth login.
All GitHub access goes through your gh CLI. Nimbalyst stores no GitHub tokens of its own. If gh is missing or signed out, Pull Request mode shows setup instructions and a recheck button.
Open Pull Request mode from the Pull Requests button in the navigation gutter or press Cmd+U. The button appears once Developer Mode is on and the workspace has a GitHub remote.
Find the Pull Request That Needs You
Use the filters above the pull request list to focus on:
Open or Closed pull requests
Awaiting my review
Created by me
With conflicts or Draft
Review Status chips, which appear when pull requests are linked to tracker items (see triage below)
Search by title or pull request number, then sort by recent activity.
Review a Pull Request
Select a pull request to open its detail view:
Conversation shows the description, inline review threads (open, resolved, and outdated), and the discussion. Add your own pull-request-level comment from the box at the bottom.
Files Changed shows the diffs with a file tree. Switch between a full-file compare view and a GitHub-style collapsed diff with unified or split layout. Very large diffs load on demand.
Commits shows the commits included in the branch, with per-commit stats and copyable SHAs.
Checks shows CI and other GitHub checks grouped by failing, in progress, and passing, with links to the details on GitHub. Results refresh on a polling interval rather than streaming live.
The header also shows the source and destination branches, linked Tracker items, review state, and merge readiness.
Review with AI
Click Review with AI to start an agent session prefilled with a review command for the pull request. The session opens in the chat pane right next to the pull request, and each prompt carries a compact PR context card so the agent knows exactly which pull request it is reviewing. If tracker items reference the pull request, the session is linked to them automatically.
The agent can inspect the pull request, explain the changes, identify risks, and suggest review feedback using the same project context and tools as your other Nimbalyst sessions.
Open the Pull Request in a Worktree
Click Open in Worktree to create (or reuse) an isolated worktree on the pull request branch and open an agent session inside it. Edits and Git operations stay separate from your main working directory, and Nimbalyst switches to Agent mode with the session ready.
Use a worktree when you want the agent to run tests, make follow-up edits, or investigate the branch without disturbing other work. See Worktrees.
Triage with Review Statuses
Pull request triage runs on Nimbalyst Trackers. Link a pull request to any Tracker item with Link tracker item in the pull request header. Once linked:
The item's workflow status appears as a status pill in the header. Click the pill to change the review status.
Rows in the pull request list show a compact status badge, and the sidebar gains matching Review Status filter chips.
You can move between the pull request, the Tracker item, and any linked AI session without searching for each one.
A common setup is a dedicated tracker type for pull requests with statuses such as Backlog, Needs Review, Inspecting, and Safe, with one item per pull request. Nimbalyst never creates these items automatically; create them yourself or ask your agent to create and link them for the open pull requests.
Merging inside Nimbalyst can also advance linked items automatically when their tracker type defines a post-merge workflow status, and a one-click hint offers the update after a pull request merges.
Comment, Approve, or Merge
Add pull-request-level comments from the Conversation tab. Inline review threads from other reviewers are shown for context but cannot be authored inline yet, and there is no request-changes action; use a comment or an approval.
Use the actions in the pull request header to approve or merge when the repository and your GitHub account allow it. Nimbalyst supports GitHub's squash, merge-commit, and rebase strategies, limited to the methods the repository allows, and always asks for confirmation before merging. For squash and merge-commit merges you can edit the commit message first.
GitHub CLI Workflow Permission
Some pull requests modify GitHub Actions workflow files. GitHub requires the CLI token to include the workflow scope before those changes can be merged.
If Nimbalyst reports that the scope is missing, run:
Complete the GitHub authorization flow, then return to the pull request and retry the merge.
Last updated