Review PR

Perform a thorough code review on the current changes. Think like a senior engineer who cares about shipping safe, maintainable software.

Correctness

• Logic errors, off-by-one bugs, race conditions
• Null/undefined handling and error propagation
• Edge cases the author might have missed

Security

• Injection (SQL, command, XSS, SSTI)
• Auth and authorization gaps
• Hardcoded secrets or credentials
• Sensitive data in logs or responses

Performance

• N+1 queries, missing indexes
• Unnecessary re-computation or memory allocations
• Blocking operations in hot paths

Code quality

• Naming accuracy and readability
• Duplication worth extracting
• Dead code or unused imports
• Overly complex logic that should be simplified

Testing

• Missing test cases for the new behavior
• Edge cases not covered
• Tests that test implementation instead of behavior

Output format

For each issue:

[SEVERITY] file:line — What the problem is Why it matters: Risk or impact Fix: Concrete suggestion

Severity: 🔴 Critical · 🟠 High · 🟡 Medium · 🔵 Low

If nothing to flag, say so clearly and call out what was done well.