bmad-review-edge-case-hunter

Exhaustive path tracing works by walking every reachable branch and boundary condition in a file or function to surface only the missing handling, ensuring no potential edge condition is overlooked during code review.

Yes, you can review a full file or function for missing boundary conditions by applying full-scope analysis when no diff is provided, making it useful for design checks, bug hunts, and review automation.

The best way to format edge case findings for review automation is to return only the missing paths as JSON findings, ensuring structured output that downstream systems can easily parse and process.

Yes, path tracing works for both function-level and file-level scope, applying branch-by-branch boundary analysis to either targeted functions or entire files when exhaustive edge case hunting is needed.

Use diff analysis when you need findings tightly scoped to a specific edit, and use full-scope analysis when no diff is available or when you need to hunt bugs across an entire file or function.