bmad-review-edge-case-hunter

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

Updated Feb 11, 2026

Search Tags:#code-review #diff-analysis #edge-case #exhaustive #path-tracing #guard-conditions

Ready to run

npx skills add https://github.com/mschuerig/peach-ios --skill bmad-review-edge-case-hunter-mschuerig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/core/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-review-edge-case-hunter-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exhaustive edge-case discovery by walking every branching path and boundary condition in the provided content, reporting only unhandled paths.

Core Features & Use Cases

Exhaustive path enumeration across diffs, full files, or functions
Guards and error-path verification for boundary conditions
Focused review output suitable for code review, specs review, and diff auditing

Quick Start

Provide the diff or code to review; the tool will enumerate all paths and report any unhandled edge cases.

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

Edge case detection works by exhaustively enumerating all control-flow paths in your code and checking for explicit guards on boundary conditions. It reports only the paths that lack proper error handling or guard conditions, ensuring deterministic analysis.

Can I trace boundary conditions and branching paths in full files, or only in diffs?▼

Yes, exhaustive path enumeration applies to full files, individual functions, and diffs across programming languages. It traces every control-flow path to verify guards and error paths for boundary conditions regardless of the input scope.

What is the best way to audit error paths and guard conditions in a new feature?▼

The best way to audit error paths is using exhaustive path tracing to walk every branching condition in your code and deterministically report only unhandled paths lacking explicit guards. This provides focused output suitable for diff auditing and specs review.

Does exhaustive path tracing work with any programming language?▼

Exhaustive path tracing works across languages by analyzing the provided content's control-flow paths and boundary conditions. It focuses on branching logic and guard verification rather than relying on language-specific syntax rules or compilers.

Why does my code review miss untested branching paths and boundary conditions?▼

Code reviews often miss untested branching paths because they lack exhaustive path enumeration. Without deterministically walking every control-flow path to verify explicit guards, unhandled boundary conditions and error routes remain unreported.