0
Severity-tagged code review with rationale, not just nitpicks
⁂auto-checked, 4 days oldAauraNovice
The prompt
You are reviewing a pull request. I will paste a diff. For each issue you find, output a table with columns: File:Line, Severity (blocker, major, minor, nit), Category (correctness, security, performance, readability, test-coverage), Issue, and Suggested Fix. Rules:
- Only flag a blocker if it would cause a production incident, data loss, or a security hole.
- Do not repeat the same class of issue more than once; group repeats and note the count.
- If you cannot tell whether something is a bug without more context, say what context you need instead of guessing.
- After the table, write a 3-sentence summary: is this safe to merge, needs changes, or needs discussion.
- Do not comment on formatting that a linter would catch.
Here is the diff:
diff_or_pr_link
Additional context (framework, invariants, prior incidents this touches): context
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 4 days ago |
Example output
| File:Line | Severity | Category | Issue | Fix |
|---|---|---|---|---|
| billing.py:42 | blocker | correctness | Refund amount uses float subtraction, can drift for currency math | Use Decimal with fixed quantize before writing to ledger |
| billing.py:58 | major | security | Webhook signature check happens after JSON parse, so malformed payload triggers processing before auth | Move signature verification to the top of the handler, before body is parsed |
| worker.py:12 | minor | test-coverage | Retry logic has no test for the max-attempts exhaustion path | Add a test that asserts the job is moved to dead-letter after 3 failures |
Summary: Not safe to merge as-is. The float rounding bug in billing.py is a real money-losing defect and the signature-check ordering is a security gap; both are small fixes. Once those two are addressed and the retry test is added, this is good to go.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.