bmad-review-edge-case-hunter

Edge case detection works by exhaustively enumerating all control-flow paths in your code and checking for explicit guards on boundary conditions. It reports only the paths that lack proper error handling or guard conditions, ensuring deterministic analysis.

Yes, exhaustive path enumeration applies to full files, individual functions, and diffs across programming languages. It traces every control-flow path to verify guards and error paths for boundary conditions regardless of the input scope.

The best way to audit error paths is using exhaustive path tracing to walk every branching condition in your code and deterministically report only unhandled paths lacking explicit guards. This provides focused output suitable for diff auditing and specs review.

Exhaustive path tracing works across languages by analyzing the provided content's control-flow paths and boundary conditions. It focuses on branching logic and guard verification rather than relying on language-specific syntax rules or compilers.

Code reviews often miss untested branching paths because they lack exhaustive path enumeration. Without deterministically walking every control-flow path to verify explicit guards, unhandled boundary conditions and error routes remain unreported.