bmad-review-edge-case-hunter

Trace control flow paths to identify unhandled edge cases in code, specs, and diffs.

Updated May 23, 2026

Search Tags:#diff analysis #software engineering #code review #validation #edge cases #boundary conditions #path tracing

Ready to run

npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-review-edge-case-hunter-diegosanchespereira1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps reviewers systematically find missing edge-case handling in code, specs, or diffs without mixing in general quality commentary.

Core Features & Use Cases

Exhaustive path tracing across branches, loops, early returns, and error handlers.
Boundary-condition analysis for nulls, empties, defaults, off-by-one ranges, and state transitions.
Ideal for reviewing patches, full files, and functions where only unhandled cases should be reported.

Quick Start

Review the provided diff or file and return only the unhandled edge cases 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?▼

Finding unhandled edge cases in a code diff requires mechanical path tracing across control flow, error handling, and halt conditions. This process reports only missing guards by analyzing branching logic, boundary conditions, and validation gaps in the provided content.

What is mechanical path tracing for boundary condition analysis?▼

Mechanical path tracing for boundary condition analysis is a software engineering review method that systematically examines branches, loops, and early returns. It identifies missing handling for nulls, empties, defaults, off-by-one ranges, and state transitions.

How do I check for missing validation gaps in software specs?▼

Checking for missing validation gaps in software specs involves exhaustive path tracing across branching logic and error handlers. It specifically targets unhandled boundary conditions and defaults to report only missing guards without general quality commentary.

Does edge case review work on full files or only patches?▼

Edge case review works on both full files and patches. The analysis applies to exhaustive review of branching logic, boundary conditions, and validation gaps in any provided content including full files, functions, and diffs.

What is the best way to review error handling and halt conditions?▼

The best way to review error handling and halt conditions is applying mechanical path tracing across the control flow. This isolates unhandled edge cases and reports only missing guards for boundary conditions and state transitions.

Why does my boundary condition review return general quality commentary?▼

Boundary condition review returns general quality commentary when not strictly limited to reporting missing guards. To avoid this, apply mechanical path tracing across control flow and error handling to exclusively report unhandled edge cases as JSON.