Goal
Provide a production-minded code review focused on real risks.
When to Use
- A change set needs review before merge or release.
- A complex feature spans several files or layers.
- Security, auth, data, or environment changes are involved.
Instructions
- Review for correctness, trust boundaries, and boundary separation.
- Identify likely regressions, missing validations, and risky duplication.
- Prioritize findings by severity and likelihood.
- Note missing tests or rollout risks.
Constraints
- Findings first, summary second.
- Do not focus on style when correctness risk is higher.
- Be explicit about assumptions.
Output Format
- prioritized findings
- open questions
- residual risks
- brief summary
Examples
- "Review this auth-related PR."
- "Do a production-minded code review of this feature."