bmad-review-edge-case-hunter

Exhaustive edge-case analysis identifies unhandled scenarios in code diffs by walking every branching path and reporting missing guard logic, null inputs, and boundary violations. It enumerates paths to reveal gaps not covered by existing conditions.

Exhaustive path enumeration is a method-driven code review technique that walks every branching path and boundary condition in a file or function. It reports unhandled edge cases, ignoring covered paths to reveal missing defaults and boundary violations.

Yes, boundary condition analysis can be applied to full files, functions, or code diffs. The analysis detects missing else statements, defaults, null or empty inputs, and boundary violations, detailing the consequences of these gaps.

Yes, edge-case analysis is suitable for rigorous reviews of both code and specifications. It applies method-driven path enumeration to specs and diffs to reveal unhandled scenarios, gaps in guard logic, and missing boundary conditions.

Method-driven edge-case analysis walks every branching path to find unhandled scenarios, whereas adversarial review is attitude-driven. It focuses strictly on enumerating paths and boundary conditions to report missing guard logic rather than challenging intent.

Use exhaustive edge-case path analysis when you need to rigorously verify that all branching paths and boundary conditions in a diff or file are handled. It is ideal for detecting missing defaults, null inputs, and boundary violations before deployment.