bmad-review-edge-case-hunter

Trace code branches and boundaries to report unhandled edge cases.

Updated Mar 24, 2026

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

Ready to run

npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-review-edge-case-hunter-imonmi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk every branching path and boundary condition in content, report only unhandled edge cases to ensure exhaustive coverage.

Core Features & Use Cases

Exhaustive edge-case enumeration: identify and document every boundary scenario that your changes could encounter.
Diff-focused analysis: enumerate unhandled edges directly reachable from changed lines when a diff is provided.
Method-driven reviews: maintain objective, coverage-first analysis without subjective judgments.

Quick Start

Provide a diff or full content to trigger exhaustive edge-case enumeration.

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 enumeration identifies unhandled boundary conditions by tracing every branch directly reachable from changed diff lines. It operates objectively on diffs, full files, or individual functions to document missing guards.

What is exhaustive path tracing for boundary conditions?▼

Exhaustive path tracing for boundary conditions is a method-driven code review technique that walks every branching path to document unhandled edge cases. It enforces deterministic reporting with exact step order and no editorial commentary.

How do I trace branching paths in full files to find missing guards?▼

You trace branching paths in full files by providing the complete file content to trigger edge-case enumeration. The analysis walks every branch and boundary condition, documenting only paths that lack explicit guards.

Can I use diff analysis to identify boundary scenarios in individual functions?▼

Yes, diff analysis can identify boundary scenarios in individual functions. The tool operates on individual functions, full files, or diffs, exhaustively tracing every branching path to report unhandled edge cases objectively.

Does this code review method provide subjective code quality feedback?▼

No, this code review method does not provide subjective code quality feedback. It maintains coverage-first, deterministic reporting with exact step order and no editorial commentary, focusing strictly on unhandled edge cases.