bmad-review-edge-case-hunter

Diff-scoped edge case analysis uses strict diff-hunk locality to inspect only changed code and its directly reachable boundaries. It reports missing guards by path-tracing branching paths, ensuring unhandled boundary conditions introduced by recent modifications are caught.

Path-tracing for boundary condition analysis is a method-driven review technique that mechanically walks branching paths to report only missing guards. It forces exhaustive enumeration of unhandled edge cases to prevent hidden software failures before deployment.

Yes, you can review a full function without a diff by using full-scope review mode. When no diff is provided, the analysis treats the entire provided content as scope to ensure no unhandled branching paths or missing boundary condition guards are missed.

To get structured JSON findings for missing guard validation, request a code review that outputs finding objects exclusively. The analysis performs order-preserving execution steps and returns a JSON-only list of unhandled edge-case paths and missing explicit guards.

Yes, diff scanning only reports missing handling in changed hunks. It applies strict diff-hunk locality rules to inspect changed code and its directly reachable boundaries, ensuring order-preserving execution steps focus exclusively on unhandled paths within the diff scope.

The best way to prevent hidden failures from unhandled edge cases is method-driven review that forces exhaustive path-tracing of branching paths and boundary conditions. This approach lists only unhandled paths and missing guards, providing explicit JSON findings for remediation.