bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, you can mechanically trace control flow and state transitions to detect missing guards and boundary conditions like off-by-one errors. This process requires structured input content to generate a JSON array of execution failure findings.

Exhaustive path analysis for software quality systematically walks through control flow, conditionals, and state transitions in code or specifications. It identifies missing error handling and boundary failures by mechanically tracing execution routes to ensure all branching paths are covered.

Detect boundary conditions like null inputs and arithmetic overflows during a code review by applying mechanical path enumeration to your code. This identifies potential execution failures by systematically tracing loops and state transitions to expose missing guards in the logic.

Yes, you can use this path analysis approach directly on software specifications. The process performs exhaustive path enumeration and boundary condition analysis on specifications to identify unhandled edge cases and missing error states before implementation begins.

The input format for boundary condition detection must be structured content, such as formatted code, specifications, or diffs. The analysis requires this structured input to mechanically trace control flow and output a JSON array of potential execution failures.