bmad-review-edge-case-hunter

Enumerate branching paths and report unhandled edge cases in code, diffs, or specs.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --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/iguanatrader/tree/main/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-review-edge-case-hunter-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Core Features & Use Cases

  • Exhaustive path analysis: enumerates all reachable boundaries from changes and flag unhandled cases.
  • Diff-aware reviews: focuses on diff hunks to surface gaps not covered.
  • Guided execution model: strictly follows the "Execution" steps to ensure deterministic review.

Quick Start

Provide the content to review (diff, full file, or function) to trigger exhaustive edge-case analysis.

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?

Exhaustive edge-case discovery analyzes code diffs by walking every branching path and boundary condition. It performs exhaustive path enumeration to report only unhandled edge cases in the changes.

What is exhaustive path enumeration for boundary conditions?

Exhaustive path enumeration is a deterministic technique that traces all reachable boundaries in code or specs. It systematically walks every branching path to flag unhandled edge cases rather than relying on adversarial guessing.

Can I use this edge-case analysis on specification documents?

Yes, you can analyze specification documents for unhandled edge cases. The tool surfaces deterministic boundary conditions and gaps not covered in spec documents, full files, or functions.

How do I perform a diff-aware code review for boundary conditions?

Perform a diff-aware code review by providing diff hunks to trigger edge-case analysis. The process focuses strictly on the provided diff hunks to surface gaps and unhandled paths not covered by the changes.

Does edge-case hunting replace adversarial code review?

Edge-case hunting is orthogonal to adversarial review. It is method-driven rather than attitude-driven, providing deterministic boundary condition tracing instead of subjective adversarial probing.

What are the limitations of method-driven edge-case analysis?

Method-driven edge-case analysis requires diff or content input to function. It strictly follows deterministic execution steps, meaning it cannot evaluate subjective code quality or find cases outside the provided paths.