bmad-review-edge-case-hunter

Identify unhandled edge cases by exhaustive path analysis of code or diffs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-review-edge-case-hunter-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/core/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-review-edge-case-hunter-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify unhandled edge cases by exhaustively enumerating all paths and boundaries in code, diffs, or specs, and reporting only those that lack explicit guards.

Core Features & Use Cases

  • Exhaustive path analysis for code, diffs, or full files to surface unhandled scenarios.
  • Treats provided content as the scope and ignores unrelated code outside the reference.
  • Generates a precise list of unguarded paths to guide review and risk mitigation.

Quick Start

Provide a sample diff or file content to review and trigger the 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?

To find unhandled edge cases in a code diff, you need exhaustive path analysis that walks every branch and boundary. This process enumerates all execution paths in diffs or full files and reports only those lacking explicit guards.

What is exhaustive path analysis for risk identification?

Exhaustive path analysis for risk identification is a software testing technique that walks every branch and boundary in code to surface unguarded scenarios. It treats the provided content as the scope and ignores unrelated code outside the reference.

Can I use edge-case review on full files or only on diffs?

You can apply edge-case review to diffs, full files, or individual functions. The analysis treats the provided content as its complete scope, enumerating paths and boundaries to reveal missing guards regardless of the input format.

How do I start an edge-case hunt for missing guards?

To start an edge-case hunt, provide a sample diff or file content to review. The analysis requires strict execution order, walking every branch to generate a precise list of unguarded paths that guide your code review and risk mitigation.

Does diff review for edge cases analyze code outside the provided reference?

No, diff review for edge cases ignores unrelated code outside the provided reference. It treats the supplied diff or file content as the exclusive scope, ensuring the reported missing guards are strictly relevant to your target code.