rcode-review-edge-case-hunter

To find unhandled edge cases in a code diff, trace every branch, early return, and loop boundary within the changed hunks to identify missing null checks and off-by-one errors. Diff-aware scoping focuses the review strictly on the modified code.

Boundary analysis in code review is the process of exhaustively tracing reachable failure paths and state transitions to ensure complete path enumeration. You need it when verifying that all boundary conditions have explicit guard checks and default handling.

To check branch coverage and trace failure paths in a full file, exhaustively enumerate all reachable paths and state transitions within the supplied scope. This process identifies missing defaults and direct failure modes without expanding beyond the input.

Yes, you can review specific functions for missing guards by limiting the scope to the supplied input. The analysis focuses strictly on the provided content, tracing branches and boundaries within that defined scope unless explicitly expanded.

The best way to get a findings-only report of missing default handling is to perform path-by-path review that requires explicit guard checks and complete path enumeration. This yields a precise list of overlooked conditions without explanatory filler.

A limitation of automated edge case hunting is that scope is strictly limited to the supplied input unless explicitly expanded by the user. It reports only unhandled boundary conditions and reachable failure paths found within the provided content.