bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, you perform systematic path tracing and boundary enumeration to surface missing guards. Diff-focused review walks control flow paths, early returns, loops, and boundary transitions directly reachable from edited lines, returning only missing handling as JSON.

Exhaustive path tracing for boundary conditions is a spec review technique that walks every reachable branch and boundary transition to identify absent defaults or missing null checks. It systematically enumerates paths to surface unhandled edge cases rather than reporting existing guards.

You can review a full file for missing guards or limit analysis to change hunks. Full-content review analyzes the entire provided scope for unhandled conditions, while diff-focused review restricts exhaustive boundary analysis directly to paths reachable from edited lines.

The best way to check a patch for off-by-one errors and missing null checks is applying diff-focused edge case hunting. It traces control flow paths directly reachable from edited lines and explicitly reports missing boundary condition guards as structured JSON.

Edge case hunting does not report all existing boundary conditions in the code. It applies exhaustive path tracing and explicit reporting of only missing guards, ensuring the review output surfaces unhandled edge cases rather than documenting already handled logic.