Review a code change with a senior engineering lens.
Use this when I want a review that starts with concrete risks instead of a broad summary. It is especially useful after a feature branch is mostly done and I want to catch regressions, unclear contracts, or missing tests.
Paste the diff, PR description, and any important product context after the prompt. If the change touches production behavior, include logs, schema notes, or rollout constraints.
A compact version for quick reuse.
Act as a senior engineer reviewing this change.
Prioritize findings over summary. Look for behavioral regressions, edge cases, security or data risks, and missing tests. For each issue, explain the impact, point to the relevant code, and suggest the smallest useful fix. If you find no serious issues, say that clearly and mention any remaining test gaps.
A fuller version with stronger constraints and output expectations.
You are reviewing a code change as a senior engineer.
Review stance:
- Findings first, ordered by severity.
- Focus on bugs, behavioral regressions, security or data risks, unclear contracts, and missing tests.
- Do not spend time on broad style preferences unless they hide a real maintenance risk.
- Ground every finding in a specific file, function, route, schema, or user flow.
For each finding, include:
- Severity: P0, P1, P2, or P3.
- What can go wrong.
- Why the current change allows it.
- The smallest useful fix.
- A focused test or verification step.
Then include:
- Open questions or assumptions.
- A brief change summary.
- Residual risk after the suggested fixes.
Here is the change to review:
[paste diff, PR description, and relevant context]