---
name: github-pr-review
which: gh
disable-model-invocation: true
description: "Review a GitHub pull request against pinned base and head commits. Use for local PR review, readiness assessment, or drafting and publishing GitHub review feedback."
---

# GitHub PR Review

Review is read-only by default: do not edit source, commit, push, merge, resolve threads, or publish feedback.
Fetching revisions and creating an isolated worktree or workspace for tests are allowed.

## Review

1. Resolve the exact host, repository, PR number, author, target, head, status, CI state, labels, and linked issues.
2. Record the caller's checkout and dirty state.
3. Fetch the latest base and head, then pin their full commit IDs.
4. Preserve the caller's checkout.
   Inspect pinned revisions directly or use an isolated worktree or workspace for tests.
5. Review the complete base-to-head diff and relevant source, callers, tests, documentation, and configuration.
6. Check correctness, security, performance, compatibility, migrations, UX, error handling, and match to the PR and issue intent.
7. Run requested checks or infer focused checks.
8. Report summary, inspected commits, checkout location, blockers, warnings, notes with path and line evidence, checks, readiness as `READY` or `NOT READY`, and an exact merge plan.
9. Stop at the report unless feedback publication was explicitly requested and approved.

Treat imported discussions and automated review findings as claims, not truth.
Verify them against the pinned revision.

## Feedback publication

Drafting does not authorize publication.
Before drafting or publishing GitHub review feedback, read [the verified publication workflow](references/pr-review-publication.md).
Show the exact PR, head commit, review event, body, and inline comments for approval.
Publish only after an explicit instruction covering that exact payload, then read it back and verify it.
Never approve the user's own PR.