skills.rest
curdx
curdxCOMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Trace branching paths and boundary conditions to find unhandled edge cases.

4|Updated Apr 26, 2026
Search Tags:#code review#verification#edge-case analysis#boundary conditions#path enumeration#diff triage
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-review-edge-case-hunter-curdx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-review-edge-case-hunter-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies missing boundary handling and unguarded branching paths so your reviews don’t miss critical failure modes.

Core Features & Use Cases

  • Exhaustive path enumeration: mechanically walks every branching path and boundary condition within scope, discarding already-handled cases.
  • Diff-scoped analysis: when given a diff, it traces only boundaries directly reachable from changed lines and lists only unhandled ones.
  • Operationally neutral reporting: produces findings only (no judgments), aimed at verification of completeness against the provided content.

Quick Start

Provide the diff or full content you want reviewed, plus optional considerations, then ask it to return only the unhandled edge-case findings 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?▼

You can find unhandled edge cases in a code diff by tracing branching paths and boundary conditions reachable from changed lines, discarding handled cases to list only unguarded failure modes.

What is exhaustive path enumeration for code review?▼

Exhaustive path enumeration for code review is mechanically walking every branching path and boundary condition within scope to verify complete conditional coverage and identify missing guards.

Can I analyze full files for missing boundary conditions or only diffs?▼

You can analyze both full files and diffs for missing boundary conditions; diff-scoped analysis traces boundaries directly reachable from changed lines while full file analysis covers all functions where correctness depends on explicit guards.

How do I get machine-readable edge case findings for verification?▼

You get machine-readable edge case findings for verification by providing code or diffs and requesting JSON output, which contains operationally neutral findings without judgments for completeness verification.

What is the best way to triage diffs for unguarded branching paths?▼

The best way to triage diffs for unguarded branching paths is performing deterministic review that exhaustively traces boundary conditions from changed lines while strictly omitting already-handled paths.

Related Skills

Explore More Software Engineering Skills→
mschuerigmschuerig

bmad-review-edge-case-hunter

Trace control-flow paths to report unhandled edge cases in code.

Community
Advanced
tronghieutronghieu
36

bmad-review-edge-case-hunter

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

Community
Advanced
MazenMradMazenMrad
1

bmad-review-edge-case-hunter

Identify unhandled edge-case paths in code and diffs.

Community
Advanced
thiagoooo34252thiagoooo34252
1

engineer-code-review

Review code for security, performance, and maintainability issues using ESLint and TypeScript.

Community
Advanced