bmad-review-edge-case-hunter

Identifies missing guards and branching paths in code, specs, or diffs via exhaustive path enumeration.

36|16|Updated May 1, 2026

Search Tags:#code review #boundary conditions #spec validation #path enumeration #edge case analysis #diff scanning

Ready to run

npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-review-edge-case-hunter-tronghieu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-review-edge-case-hunter-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you find missing boundary checks and unhandled control-flow paths in a diff or provided content so reviews don’t miss critical edge conditions.

Core Features & Use Cases

Exhaustive path enumeration: Mechanically walks branching paths and boundary conditions within the given scope.
Diff-scoped review: When given a diff, it scans only affected hunks and reports only reachable boundaries from changed lines without explicit guards.
Unhandled-only reporting: Produces findings exclusively for gaps in handling, with no editorial commentary.

Quick Start

Ask your AI to review the provided diff for unhandled branching paths and boundary conditions using the edge-case hunter method.

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 and missing boundary checks in my code diff?▼

To find unhandled edge cases in a code diff, you can use an exhaustive path enumeration method that mechanically walks branching paths and reports only reachable boundaries from changed lines missing explicit guards. The output is provided as strict JSON findings.

What is exhaustive path enumeration for boundary condition analysis?▼

Exhaustive path enumeration for boundary condition analysis is a technique that mechanically walks all branching execution paths within a given scope to identify missing guards and unhandled control-flow paths. It outputs only the unhandled edge-case findings without editorial commentary.

How do I validate spec execution paths for missing control-flow guards?▼

You validate spec execution paths by providing the content scope and optional considerations to an edge-case hunter, which exhaustively enumerates reachable paths and outputs unhandled branching paths in strict JSON. This requires specifying the content scope to analyze.

Can I review only the affected hunks in a diff for unhandled branching paths?▼

Yes, you can review only affected hunks in a diff for unhandled branching paths. Diff-scoped review scans only the changed lines and reports reachable boundaries lacking explicit guards without analyzing the entire file. This applies to review scenarios involving changed lines, full functions, or entire files.

What is the best way to scan a full function for missing boundary behavior guards?▼

The best way to scan a full function for missing boundary behavior guards is applying an edge-case analysis method that enumerates all reachable execution paths and outputs only the unhandled edge-case findings in strict JSON. This ensures reviews do not miss critical edge conditions.

Does edge case analysis output include general code review commentary?▼

No, edge case analysis output does not include general code review commentary. It produces findings exclusively for gaps in handling, outputting only unhandled edge-case findings in strict JSON format. There is no editorial commentary included in the results.