bmad-review-edge-case-hunter

Walks every branching path in code or diffs and reports unhandled edge cases as JSON.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-review-edge-case-hunter-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-review-edge-case-hunter-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss boundary conditions and unguarded branches, letting subtle bugs like off-by-one errors, null inputs, and race conditions slip into production. This Skill mechanically enumerates every path in a diff, file, or function and reports only the conditions lacking explicit handling. ## Core Features & Use Cases - Exhaustive Path Enumeration: Walks all control flow branches and domain boundaries, deriving edge classes from the content itself rather than a fixed checklist. - Diff-Aware Scoping: When given a diff, analyzes only changed hunks and boundaries directly reachable from changed lines. - Structured JSON Output: Returns findings as a strict JSON array with location, trigger condition, guard snippet, and potential consequence for each unhandled path. - Use Case: Before merging a pull request, run this review on the diff to catch missing else branches, unguarded null inputs, and timeout gaps that a standard style review would overlook. ## Quick Start Ask the AI to run an edge-case review on your code diff or function and return the unhandled boundary conditions as JSON.

Frequently Asked Questions about bmad-review-edge-case-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find unhandled edge cases in a code diff?▼

Provide the diff as input and the review scans only the changed hunks, listing boundaries directly reachable from changed lines that lack an explicit guard. Findings are returned as a JSON array with location, trigger condition, guard snippet, and consequence.

What kinds of edge cases does an edge case review detect?▼

It derives edge classes from the content itself, covering missing else or default branches, unguarded null or empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, and timeout gaps.

Can I review a full file instead of a diff for edge cases?▼

Yes, when no diff is provided the entire file or function becomes the analysis scope. The rest of the codebase is ignored unless the provided content explicitly references external functions.

What output format does the edge case review produce?▼

It returns only a valid JSON array where each object has exactly four fields: location, trigger_condition, guard_snippet, and potential_consequence. An empty array is returned when no unhandled paths are found.

When should I not use edge case hunting for code review?▼

It is not suited for judging code quality, style, or architecture since it deliberately never comments on whether code is good or bad. Use it alongside adversarial or design reviews, not as a replacement for them.