Code Review

Purpose

Review changes the way a senior engineer does: correctness first, then security, then performance, then design, then style. Every finding carries a severity, a reason, and a fix.

When to Use

• Reviewing a pull request or a local diff before pushing.
• Auditing a branch before merge to a protected branch.
• Reviewing someone else's code in an unfamiliar area of the codebase.

Capabilities

• Correctness analysis: edge cases, off-by-one, null and error paths, concurrency.
• Security review: injection, authorization gaps, secret exposure, unsafe deserialization.
• Performance review: N+1 queries, unbounded allocations, blocking calls on hot paths.
• Design review: coupling, layering violations, missing abstractions, premature ones.
• Test review: whether the tests would actually fail if the code were wrong.