bmad-review-edge-case-hunter

Edge-case analysis for security-critical applications involves exhaustively walking every branching path and boundary condition to identify unhandled conditions. This ensures no potential security vulnerabilities or unexpected behaviors are overlooked during code reviews.

Yes, you can perform edge-case analysis on full files or functions, not just diffs. The analysis walks every branching path and boundary condition within the provided content to identify and report any unhandled edge cases.

Yes, edge-case analysis supports full files and functions. You can provide full content instead of diffs, and the analysis will walk every branching path and boundary condition to identify unhandled edge cases.

Edge-case analysis works with both full files and diffs. It can process full files, functions, or diffs to walk every branching path and boundary condition, identifying and reporting unhandled edge cases in a structured JSON format.

The edge-case analysis output uses a structured JSON array format. It identifies unhandled edge cases by walking every branching path and boundary condition, providing the findings in a structured JSON array for easy integration into code reviews.

You need exhaustive edge-case analysis for code reviews when dealing with security-critical applications or complex algorithms. It walks every branching path and boundary condition to ensure no unhandled conditions are overlooked, providing findings in a structured JSON format.