bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, you can use an exhaustive path enumeration method that mechanically walks branching paths and reports only reachable boundaries from changed lines missing explicit guards. The output is provided as strict JSON findings.

Exhaustive path enumeration for boundary condition analysis is a technique that mechanically walks all branching execution paths within a given scope to identify missing guards and unhandled control-flow paths. It outputs only the unhandled edge-case findings without editorial commentary.

You validate spec execution paths by providing the content scope and optional considerations to an edge-case hunter, which exhaustively enumerates reachable paths and outputs unhandled branching paths in strict JSON. This requires specifying the content scope to analyze.

Yes, you can review only affected hunks in a diff for unhandled branching paths. Diff-scoped review scans only the changed lines and reports reachable boundaries lacking explicit guards without analyzing the entire file. This applies to review scenarios involving changed lines, full functions, or entire files.

The best way to scan a full function for missing boundary behavior guards is applying an edge-case analysis method that enumerates all reachable execution paths and outputs only the unhandled edge-case findings in strict JSON. This ensures reviews do not miss critical edge conditions.

No, edge case analysis output does not include general code review commentary. It produces findings exclusively for gaps in handling, outputting only unhandled edge-case findings in strict JSON format. There is no editorial commentary included in the results.