Code review that catches bugs: data flow, edge cases, errors, concurrency, security
Most review comments are about naming and style, while the bugs walk past. How we review for correctness instead: follow the data, probe edge cases and error paths, look for races and trust boundaries, keep PRs small and hand style to machines.