bmad-review-edge-case-hunter

You enumerate branching and boundary-condition paths within the provided diff hunks to identify missing guard conditions. This method reports only unhandled edge cases in strict JSON format without evaluating overall code quality.

Boundary testing for unhandled edge cases systematically enumerates branching paths to detect silent failures. It traces reachable boundary paths lacking explicit guards within provided code content or diff hunks.

Yes, when no diff is provided, the analysis treats the entire provided content as the scope. It enumerates all branching and boundary conditions within that full content to find missing guards.

You get structured JSON reporting for missing guards by executing path enumeration on your diff and requesting a JSON-only findings output. This enforces a strict output contract containing only unhandled paths and conditions.

Diff analysis path enumeration is strictly limited to the provided diff hunks. It scans only those modified sections to enumerate reachable boundary paths, ensuring findings are scoped exclusively to the changes.

No, the edge case detection is method-driven and reports only unhandled paths and conditions. It strictly avoids evaluating whether the code is good or bad, focusing solely on missing boundary guards.