bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, perform exhaustive path analysis on the changes to mechanically enumerate control flow and domain boundaries. This identifies conditions lacking explicit handling without subjective bias.

Mechanical path enumeration for edge case analysis is a method that focuses on paths and conditions lacking explicit handling rather than subjective judgment. It systematically checks control flow and domain boundaries to ensure thorough coverage.

Yes, you can analyze specification documents for potential vulnerabilities without external dependencies using automated edge case analysis. The process requires no external dependencies for basic functionality, focusing on exhaustive path analysis to identify oversights.

Yes, edge case analysis works for both full codebase review and diff inspection. It performs exhaustive path analysis on code, specs, or diffs to identify unhandled conditions, ensuring no potential issues are overlooked during regular reviews.

Regular code review misses potential oversights because it relies on subjective judgment, whereas path analysis catches them through mechanical enumeration of control flow and domain boundaries. This method-driven approach focuses on paths lacking explicit handling to find vulnerabilities not evident normally.

The best way to identify unhandled domain boundaries in specifications is to perform exhaustive path analysis using a method-driven approach. This mechanically enumerates paths and conditions lacking explicit handling, ensuring thorough edge-case coverage without subjective bias.