bmad-review-edge-case-hunter

You can find unhandled edge cases in a code diff by running an edge case analysis that walks through every branching path and boundary condition. This process reports only unhandled paths without editorializing.

Analyzing specifications for boundary conditions involves a method-driven review that walks through all potential paths. This ensures thorough review and verifies that potential security vulnerabilities are not overlooked.

You can analyze diffs, full files, or functions based on the provided content. The edge case analysis scope flexibly adjusts to inspect whatever content you supply.

No, this edge case analysis requires no external libraries for path analysis. It independently walks through branching paths and boundary conditions to report unhandled scenarios.

You identify potential security vulnerabilities during a code review by performing a comprehensive edge case analysis. This method walks through all boundary conditions to ensure potential vulnerabilities are not overlooked.

You need a method-driven review for unhandled paths when reviewing code changes or specifications. It focuses strictly on the process to report unhandled paths without editorializing.