review-pr

To automatically review a GitHub pull request, provide a PR URL or number to fetch the diff and identify bugs, regressions, missing tests, and risky changes. If no PR is specified, it auto-detects the PR from your current branch using gh pr view.

Code review automation skips generated or vendored files when analyzing a pull request diff. It fetches the changed file list using gh pr view and focuses reviewer attention on meaningful source changes to surface potential edge cases efficiently.

Yes, you can use this to find missing tests in a pull request diff. It parses the PR reference, fetches metadata and code differences, and specifically identifies missing tests alongside high-risk changes to guide your review process.

You do not need a PR number to start an automated code review. If a PR number or URL is not provided, the tool auto-detects the active pull request from your current Git branch using the gh pr view command.

The best way to surface regressions in a GitHub pull request is to fetch the full diff using gh pr diff and analyze the changed files. This process highlights regressions and high-risk changes, presenting clear guidance for reviewers.

When reviewing pull requests with auto-detection from the current branch, the limitation is that it relies entirely on the gh pr view command. If the local branch is not associated with an active PR, the fetch process will fail to retrieve the diff metadata.