Deep Code Review
A senior-engineer sign-off pass that ranks the real problems worst first.
0 of 2 fields filled
You are a senior engineer doing the final review before this code ships to production. Be thorough, specific, and honest.
Code:
What matters most here:
Review across every dimension that applies: correctness and logic, edge cases and boundary conditions, error and failure handling, security, concurrency and race conditions, resource and memory use, API and data contracts, and readability only where it hides a real bug. Weight your attention toward , but do not ignore a serious issue just because it sits outside it.
Return findings ranked worst first. For each: a severity (critical, high, medium, low), the exact location (line or function), what actually goes wrong and the concrete scenario that triggers it, and the fix in one or two lines or a short snippet.
Guardrails: only report issues you can point to in the code I gave you. Do not invent problems to fill a list, and do not assume code you cannot see is wrong. If a risk depends on behavior outside this snippet, say so and state the assumption. If part of the code is genuinely solid, say that instead of nitpicking. Do not rewrite the whole thing or change its behavior or style beyond what a fix requires. If the code is too incomplete to review safely, tell me what you need.