review-edge-case-hunter

To find unhandled edge cases in a code diff, you can analyze the supplied changes for exhaustively traced branching paths, loops, error handlers, and input boundaries. This process exposes missing null checks, timeout coverage, and default branches by reporting only unhandled conditions with their trigger conditions and potential consequences.

Tracing boundary conditions and control flow during a code review requires methodically walking branching paths, early returns, and domain boundaries. This approach isolates unhandled paths and missing safeguards, ensuring that invalid inputs and race conditions are caught by applying strict scope control to the explicitly provided content.

Yes, you can check for missing error handling in specific functions by performing a scope-aware review of the explicitly referenced content. This targeted analysis inspects the function's control flow and error handlers to identify unhandled paths and generate guard sketches without scanning the entire codebase.

You get structured JSON findings for unhandled paths by analyzing the pull request diff and requesting the output as a required JSON array. The analysis reports exact locations, trigger conditions, guard snippets, and potential consequences for each unhandled edge case discovered within the provided changes.

Yes, edge case analysis works on race conditions and timeout behavior by applying exhaustive reviews of control flow and domain boundaries. It systematically traces these specific conditions within the explicitly provided content to expose missing safeguards and report their potential consequences.

The limitation of automated path analysis for finding missing safeguards is that it requires strict scope control, meaning it only analyzes explicitly supplied diffs, files, or functions. It cannot infer context from unprovided code and relies entirely on ordered analysis steps and halt-condition handling to prevent unbounded scanning.