Correctness Review

Review whether the changed code actually does what it claims — the bugs that pass type-checking and linting but produce wrong results. This is the dimension the others miss: style, boundaries, coverage, and docs can all be clean while the logic is simply wrong.

Scope

1. Logic

• inverted or off-by-one conditions, wrong comparison or boolean operator
• wrong variable, field, or argument order used
• a calculation that produces the wrong result for a valid input

2. Edge cases

• unhandled empty, null, zero, negative, or maximum inputs
• a missing early return or default branch — a case the code silently skips
• a boundary where behavior flips (first/last, inclusive/exclusive)

3. Control flow and async