correctness-reviewer

To detect race conditions and state management bugs in a pull request, review the code by tracing control flow and checking state transitions. This surfaces concurrency issues and flags left in erroneous states before release.

The best way to check error propagation is to trace failure paths and identify swallowed exceptions or mis-mapped error codes. This detects fallback behavior that masks failures and prevents silent issues in production.

Trace execution paths by mentally executing code branches to expose off-by-one errors and boundary math mistakes. This execution tracing identifies incorrect branching and validates behavioral correctness in critical modules.

Yes, you can review code snippets for logic errors and output findings as JSON. The review traces control flow and checks boundary conditions, returning reproducible correctness issues matching a specified JSON schema.

Code passes unit tests but fails silently in production due to subtle logic errors, broken error propagation, and race conditions that standard tests miss. Reviewing state transitions and error mapping exposes these hidden behavioral faults.