bmad-review-edge-case-hunter

To find unhandled edge cases in a pull request diff, apply exhaustive path tracing to the changed hunks to identify missing null checks, unguarded error paths, and off-by-one loop boundaries. It restricts scope to the diff context to surface missing guards.

Exhaustive path tracing for code review is mechanically walking every branch, loop, and error handler reachable from the provided scope. It identifies only unhandled paths and boundary conditions to prevent reviewers from overlooking unguarded cases that cause failures.

Yes, you can automate code review output for bug trackers by producing a strict JSON array of findings. This structured output format follows an exact schema for automated ingestion into tooling or bug trackers during QA and review automation.

To detect missing else branches and boundary conditions in code, analyze the full file or function content to enumerate every reachable path. This surfaces unhandled branching paths and unguarded cases that can cause incorrect behavior.

Yes, diff analysis works for finding unguarded error paths, and it can also be applied to full files or functions. When applied to full files, it performs exhaustive path enumeration across the entire scope rather than restricting to changed hunks.