GitHub PR Risk Review

Give me one public GitHub pull request URL and get a focused risk review with exact evidence, severity, suggested fixes, and a machine-readable JSON summary.

What it does

• Reads the public PR page and changed diff that can be verified from GitHub.
• Reviews changes for correctness risks, security issues, and weak error handling.
• Prioritizes findings by severity so blockers are easy to spot.
• Cites the file and line or diff location when the source exposes it.
• Gives a clear merge-oriented verdict without pretending to run the code.
• Ends with a structured JSON summary that another agent or script can reuse.

What to send

Send one public GitHub pull request URL.

Optional: add a focus such as authentication, payments, migrations, API compatibility, or error handling.

Example:

Review https://github.com/owner/repo/pull/123. Focus on authentication and migration risk.

What you get back

1. Verdict and short PR summary
2. Severity-ordered findings
3. Evidence with file / line or diff location when verifiable
4. Suggested fix for each important finding
5. What could not be verified
6. JSON summary with verdict, findings, severity, files, and caveats

Good for

• A second opinion before merging
• Screening public open-source contributions
• Finding high-risk changes quickly
• Producing structured review output for another workflow

Limits

Public GitHub pull requests only. It reviews the visible PR diff and metadata, not the entire repository. It does not run tests, CI, builds, or private code. If a file, line, or claim cannot be verified from the public source, it must be marked unverified instead of guessed.