PR Reviews

PR reviews are the right fit when you want Atlas Review tied directly to a GitHub pull request.

Best For

• explicit pull request targeting
• GitHub publication paths
• PR-native reviewer and check context

MCP Targeting

Shared tools can target PR review explicitly with:

• reviewType: "pr_review"
• prReviewId
• githubPrNumber

Current-review fallback should only use PR review automatically when the current branch maps to exactly one PR review. Ambiguous PR context should be disambiguated explicitly instead of guessed.

Execution Model

• atlas_review_run_current for PR review is queue-only
• mode: "immediate" is rejected for PR review scope
• PR review publishing should use the PR-native publish flow after the review snapshot is ready

Example Walkthrough

A typical PR review flow looks like this:

1. Open the project that maps to the repository you want to review.
2. Select the PR review target explicitly when branch-to-PR mapping is not unique.
3. Queue the PR review and wait for the review snapshot to finish.
4. Read the summary, verdict, and findings tied to that PR snapshot.
5. Fix or dismiss findings with rationale.
6. Publish the review to GitHub only when the snapshot is current and eligible for publication.

Use PR review when the review output needs to live with the pull request, not just with your local branch iteration loop.