review-edge-case-hunter

To find unhandled edge cases in a code diff, provide the diff content for exhaustive path analysis. The traversal reports all unhandled control-flow paths reachable from the changed code with explicit guards.

Exhaustive path analysis for code reviews is a method-driven technique that walks every branching path and boundary condition. It reports only unhandled edge cases, contrasting with adversarial review by relying on deterministic execution steps.

Yes, you can use static analysis to audit unhandled paths in a full file. The analysis traverses all control-flow paths within the provided file content and reports unhandled edge cases requiring precise remediation.

To trace boundary conditions in a function, provide the function code for exhaustive edge-case tracing. The analysis enumerates all branching control-flow paths and reports unhandled guards to improve code reliability.

Use exhaustive edge-case tracing when you need method-driven analysis of all control-flow paths rather than attitude-driven adversarial review. It is suitable for diff audits, code reviews, and spec verification to find unhandled boundary conditions.

Edge-case analysis of a code path requires clearly defined inputs and deterministic execution steps. You provide the content to review, such as a diff, full file, or function, and receive a JSON list of unhandled edge-case paths.