bmad-review-edge-case-hunter

Edge case analysis identifies unhandled boundaries and state transitions in code changes. It exhaustively traces branches and boundaries in diffs or full files to output missing guards and error paths in structured JSON.

To check a patch for missing null checks and default branches, apply diff-aware path tracing to the changed hunks. This systematically identifies absent error handling and returns only the unhandled paths.

Yes, you can review a full file for missing error paths and boundary conditions. The analysis applies to full files or individual functions, exhaustively tracing state transitions to find missing guards while keeping scope limited to the supplied content.

Edge case hunting works on both individual functions and complete diffs. It requires precise scope limiting to the supplied content, whether that is a full file, a single function, or specific diff hunks, ensuring findings are tightly scoped.

The best way to trace state transitions for missing guards is exhaustive path tracing. By walking every branch and boundary in the provided scope and outputting only unhandled paths in structured JSON, you systematically spot failures before they occur.