skills.rest
enigmaicon-eng
enigmaicon-engCOMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Enumerate branching paths and boundaries to identify missing edge-case handling.

1|Updated May 16, 2026
Search Tags:#code review#boundary conditions#spec validation#path enumeration#edge case analysis#diff scanning
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-review-edge-case-hunter-enigmaicon-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/core-skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-review-edge-case-hunter-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies unhandled edge cases and missing boundary guards by mechanically enumerating reachable branching paths and conditions within the provided content scope.

Core Features & Use Cases

  • Deterministic path enumeration: Walks every branching path and boundary condition, reporting only missing handling.
  • Diff-aware scope control: When given a diff, it analyzes only diff hunks and boundaries directly reachable from changed lines.
  • Scope-safe review: When no diff is provided, it treats the full provided content as the scope and ignores unrelated codebase parts.

Quick Start

Use bmad-review-edge-case-hunter to analyze the provided diff of a function and return only the unhandled boundary conditions it introduces.

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 review?▼

To find unhandled edge cases in a code review, you mechanically enumerate reachable branching paths and boundary conditions within your provided scope to report only missing handling logic.

What is the best way to check for missing boundary guards in a diff?▼

Checking for missing boundary guards in a diff is best done by analyzing only the diff hunks and boundaries directly reachable from changed lines to focus strictly on unhandled conditions.

Can I review full file contents for edge cases when no diff is available?▼

Yes, you can review full file contents for edge cases when no diff is available, treating the entire provided content as the scope while ignoring unrelated codebase parts.

How does path enumeration work for spec validation?▼

Path enumeration for spec validation works by exhaustively walking every branching path and boundary condition within the provided content scope to identify missing handling and unhandled conditions.

What format do edge case analysis findings need to be in?▼

Edge case analysis findings need to be emitted in a required JSON schema, outputting only the discovered missing boundary handling and unhandled conditions from the review scope.

Related Skills

Explore More Software Engineering Skills→
tronghieutronghieu
36

bmad-review-edge-case-hunter

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

Community
Advanced
thuantan2060thuantan2060

bmad-review-edge-case-hunter

Enumerate branching paths and boundary conditions to detect missing guards in code.

Community
Intermediate
cassioalexandrecassioalexandre
2

bmad-review-edge-case-hunter

Enumerate branching and boundary-condition paths in code diffs to find unhandled edge cases.

Community
Advanced
MarkusonMarkuson

bmad-review-edge-case-hunter

Trace control flow and state transitions to detect unhandled edge cases.

Community
Advanced