bmad-review-edge-case-hunter

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

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-review-edge-case-hunter-mathematicguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/MathematicGuy/team-006-vin20k/tree/main/.agent/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-review-edge-case-hunter-mathematicguy

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, or race conditions slip into production. This Skill mechanically enumerates every branching path in a diff, file, or function and reports only the paths lacking explicit handling. ## Core Features & Use Cases - Exhaustive Path Enumeration: Walks all control flow (conditionals, loops, error handlers, early returns) 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; ignores the rest of the codebase. - 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, or timeout gaps that human reviewers overlooked. ## Quick Start Ask the AI to run an edge-case review on your code diff or function and list only the unhandled boundary conditions.

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, walking every branch reachable from the changed lines. It returns a JSON array of boundaries lacking explicit guards, including a minimal code sketch to close each gap.

What types 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 same exhaustive path enumeration applies, and only unhandled paths are reported.

How is edge case hunting different from adversarial code review?▼

Edge case hunting is method-driven, mechanically enumerating every branching path rather than relying on intuition or attitude. It never comments on code quality and reports only paths lacking handling.

What output format does the edge case review produce?▼

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