bmad-review-edge-case-hunter

Exhaustive path tracing identifies unhandled edge cases in a pull request diff by mechanically walking every branching path and boundary condition in the changed hunks. It delivers structured JSON output detailing location, trigger condition, minimal guard snippet, and potential consequence for each finding.

Exhaustive path tracing is a code review mechanism that mechanically walks every branching path and boundary condition in code or technical specifications. It eliminates intuition-based gaps by strictly focusing on missing edge case handling without providing editorial commentary on code quality.

You can analyze a full file for boundary conditions because the review scope adjusts automatically based on input type. For full files or functions, it analyzes the entire provided content, whereas for diffs, it restricts scanning only to changed hunks for reachable unhandled paths.

Yes, the edge case hunter works across any programming language or technical domain. It applies function-level edge case hunting and boundary checking to code, technical specifications, and version control diffs regardless of the specific language used.

The best way to prevent boundary condition bugs is to run an automated edge case hunt on the new payment processing function diff. This catches unhandled edge cases like null transaction amounts, currency boundary limits, or missing timeout guards and provides minimal guard snippets.