mh-review-edge-case-hunter

To find unhandled edge cases in a code diff, you can analyze the diff hunks for unguarded inputs, off-by-one errors, and arithmetic overflows. This edge-case analysis reports only unaddressed branching paths and boundary conditions.

Edge-case analysis in static code review is the process of walking every branching path and boundary condition within code, specs, or full files. It identifies unguarded inputs and arithmetic overflows, reporting only unhandled edge cases.

You can run edge-case analysis on both diffs and full files. The analysis identifies the scope accordingly, whether you provide entire files, functions, or specific diff hunks to evaluate for unhandled edge cases.

Yes, edge-case analysis detects off-by-one errors and arithmetic overflows. It focuses on unguarded inputs and other common issues, walking every branching path to report only unhandled edge cases.

Automated edge-case analysis for code safety requires inputs to be complete and decodable text. It operates only on the provided content, identifying unaddressed paths without modifying the original code or specifications.