bmad-review-edge-case-hunter

To find unhandled edge cases in a pull request diff, perform exhaustive path tracing and boundary condition analysis to systematically identify missing guard clauses and unhandled logic branches before merging.

Exhaustive path tracing for code review mechanically traces control flow and domain boundaries to detect missing guards, identifying unhandled members of fixed sets like enums, status codes, and implicit state transitions.

To check if deleted code creates regressions during static analysis, perform deletion impact assessment to validate that removed code does not create orphaned references or break existing control flow paths.

Yes, static analysis can detect implicit branches and unhandled enums by applying a multi-step verification method that identifies unhandled members of fixed sets, status codes, and flags within your control flow.

You need boundary condition analysis and path tracing for software engineering workflows requiring rigorous validation of control flow, error handling, and state transitions to eliminate oversight in code reviews.

Automated edge case detection for debugging requires strict adherence to multi-step verification methods and may not replace human intuition for complex domain logic, focusing primarily on mechanical control flow and boundary validation.