bmad-review-edge-case-hunter

Trace all branching paths in code diffs to report unhandled edge cases.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-review-edge-case-hunter-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-review-edge-case-hunter-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Core Features & Use Cases

  • Exhaustive path tracing across diffs, full files, or functions to surface unhandled conditions.
  • Focused reporting that highlights gaps and unguarded branches for remediation.
  • Suitable for code reviews, specs validation, and change-impact analysis.

Quick Start

Run the edge-case hunter on the target diff or file to enumerate unhandled paths.

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 path tracing maps every reachable area and boundary condition in your code diff, surfacing only unhandled branches so you can add explicit guards to close gaps.

What is exhaustive path tracing for boundary conditions?

Exhaustive path tracing is a method-driven analysis technique that walks every branching path in full files or functions to map boundary conditions and identify unguarded branches.

Can I use edge case analysis on full files or only function snippets?

You can apply edge case analysis to full files, individual functions, or code diffs; the tracing process maps all reachable areas and boundary conditions regardless of input scope.

How does method-driven edge case hunting differ from adversarial code review?

Method-driven edge case hunting is orthogonal to adversarial review because it focuses on exhaustively tracing all reachable paths to find gaps, rather than relying on an attitude-driven critique.

When do I need to trace boundary conditions in my code?

You need to trace boundary conditions during code reviews, specs validation, or change-impact analysis to ensure all branching paths have explicit guards and no unhandled conditions remain.

Does path tracing report all reachable areas or only unhandled branches?

Path tracing reports only unhandled branches and unguarded conditions found in the diff hunks, requiring explicit guards for remediation rather than listing all successfully traced paths.