bmad-review-edge-case-hunter

Finding unhandled edge cases in a code diff requires mechanical path tracing across control flow, error handling, and halt conditions. This process reports only missing guards by analyzing branching logic, boundary conditions, and validation gaps in the provided content.

Mechanical path tracing for boundary condition analysis is a software engineering review method that systematically examines branches, loops, and early returns. It identifies missing handling for nulls, empties, defaults, off-by-one ranges, and state transitions.

Checking for missing validation gaps in software specs involves exhaustive path tracing across branching logic and error handlers. It specifically targets unhandled boundary conditions and defaults to report only missing guards without general quality commentary.

Edge case review works on both full files and patches. The analysis applies to exhaustive review of branching logic, boundary conditions, and validation gaps in any provided content including full files, functions, and diffs.

The best way to review error handling and halt conditions is applying mechanical path tracing across the control flow. This isolates unhandled edge cases and reports only missing guards for boundary conditions and state transitions.

Boundary condition review returns general quality commentary when not strictly limited to reporting missing guards. To avoid this, apply mechanical path tracing across control flow and error handling to exclusively report unhandled edge cases as JSON.