bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, you need exhaustive path analysis to walk every branching path and boundary condition within the provided content, revealing only the unhandled cases.

Exhaustive path analysis for boundary conditions is a code review technique that enumerates every potential branch and input boundary within a function or file, reporting only the unhandled paths to ensure comprehensive coverage of edge conditions.

To review a full file for unhandled branches, provide the complete file content to the edge-case analysis process, which will enumerate every potential branch and input boundary while ignoring already-handled paths.

Yes, you can use path analysis to check a specific function body for edge cases by providing just the function code, allowing the review to walk every branching path within that isolated scope to reveal unhandled conditions.

No, edge-case tracing does not evaluate code quality or design patterns, as it operates strictly to enumerate unhandled paths and boundary conditions while avoiding speculative judgments about the overall code design.