bmad-review-edge-case-hunter

To find unhandled edge cases in a code diff, you need exhaustive path enumeration and boundary condition analysis. This process mechanically walks every control flow and domain boundary in the diff hunks to identify and report branching paths that lack proper handling.

Boundary condition analysis in software testing is the process of mechanically tracing every control flow and domain boundary within code or specifications. It identifies unhandled branching paths to ensure complete test coverage and robust software before complex features are merged.

Yes, you can use path tracing to review specifications instead of source code. The analysis performs exhaustive path enumeration and boundary condition identification on provided content, which is applicable to code, specifications, or diffs to ensure complete test coverage.

The best way to ensure complete test coverage for complex features is performing exhaustive path enumeration and boundary condition analysis on the new code. This mechanical path tracing identifies and reports unhandled edge cases before the feature merge.

Yes, differential review targets only the changed diff hunks. It focuses exhaustive path enumeration and boundary condition analysis specifically on the provided diff content to identify unhandled edge cases for targeted code reviews.