bmad-review-edge-case-hunter

To find unhandled edge cases in your code diffs, exhaustive path tracing analyzes branches and surfaces missing guard conditions without subjective commentary. It evaluates diffs, full files, or functions to report only unguarded execution paths.

Exhaustive path tracing for code review is a deterministic technique that enumerates all execution branches to identify missing guards. It surfaces unhandled edge cases across full files or diffs, providing objective analysis without subjective code judgments.

Yes, you can use edge-case path tracing on individual functions. The analysis works on full files, individual functions, or diffs to deterministically surface missing guard conditions across all branches and report unhandled paths.

The best way to review diffs for missing guard conditions is applying deterministic path tracing to enumerate every execution branch. This approach reveals unhandled edge cases by strictly reporting unguarded paths without adding subjective code quality commentary.

No, exhaustive path tracing does not provide subjective code quality feedback. It adheres to explicit execution steps to deterministically report only unhandled paths and missing guards, ensuring a focused review of edge cases rather than style commentary.

To identify missing guard conditions across code branches, exhaustive path tracing maps all execution paths to reveal unguarded scenarios. It operates on diffs or full files to report unhandled edge cases deterministically.