bmad-review-edge-case-hunter

Analyze code, specifications, or diffs for unhandled edge cases.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Dydyy-y/react-native --skill bmad-review-edge-case-hunter-dydyy-y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/Dydyy-y/react-native/tree/main/projet/.github/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/Dydyy-y/react-native --skill bmad-review-edge-case-hunter-dydyy-y

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides thorough edge-case analysis, ensuring that all branching paths and boundary conditions are covered, leaving no unhandled edge cases in code, specs, or diffs.

Core Features & Use Cases

  • Exhaustive Path Analysis: Mechanically walk every branch and boundary condition, reporting only unhandled paths.
  • Handling Diffs and Full Content: Scan diffs, full files, or functions, and treat provided content as the scope.
  • Use Case: For code reviews, use this Skill to identify unhandled edge cases in a diff, ensuring thorough testing coverage.

Quick Start

Run the 'bmad-review-edge-case-hunter' skill on the latest code diff to analyze for 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?

To find unhandled edge cases in a code diff, you can perform an exhaustive path analysis that mechanically walks every branch and boundary condition, reporting only the paths lacking explicit handling.

What is edge-case analysis for code reviews?

Edge-case analysis for code reviews is the process of targeting all reachable paths and boundary conditions in a diff or full file to ensure thorough testing coverage and identify unhandled scenarios.

Do I need Python to run security auditing and path tracing on my code?

Yes, you need Python installed in your environment, because the execution and analysis logic for this edge-case path tracing and security auditing requires Python to run.

Can I analyze full files and functions instead of just diffs for boundary conditions?

Yes, you can analyze full files and functions by treating the provided content as the scope, allowing the boundary condition analysis to scan either diffs or complete code structures.

What's the best way to ensure complete branch coverage in specifications?

The best way to ensure complete branch coverage in specifications is to perform an exhaustive path analysis that targets all reachable paths and excludes only those with explicit handling.