bmad-review-edge-case-hunter

Identify unhandled edge-case paths in code and diffs.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-review-edge-case-hunter-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-review-edge-case-hunter-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies unhandled edge cases and defensive gaps in code, diffs, and content, ensuring comprehensive review coverage.

Core Features & Use Cases

  • Exhaustive path enumeration across branching conditions and inputs.
  • Detects missing guards and unmet error-handling scenarios in code and diffs.
  • Provides structured findings focused solely on unhandled paths.

Quick Start

Review the provided content and exhaustively enumerate all 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?

Exhaustive path analysis identifies unhandled edge cases in code diffs by tracing branching points, inputs, and domain boundaries lacking guards. It reviews provided content to detect defensive gaps and outputs structured findings focused solely on unhandled paths.

What is exhaustive path tracing for code reviews?

Exhaustive path tracing for code reviews is a method to enumerate all branching conditions and inputs to detect missing guards. It ensures comprehensive coverage by identifying unmet error-handling scenarios and defensive gaps across the provided code or diff content.

How do I detect missing error handling scenarios in my code?

Detect missing error handling scenarios by applying exhaustive path enumeration across branching conditions and inputs. This analysis identifies domain boundaries without guards and outputs structured findings exclusively for unhandled paths within the provided content.

Does edge-case detection work on existing code or only on new diffs?

Edge-case detection works on both existing code and new diffs. The analysis applies to any provided content, exhaustively enumerating unhandled paths and missing guards across branching conditions and domain boundaries regardless of format.

What is the best way to review code for defensive gaps?

The best way to review code for defensive gaps is to perform exhaustive path analysis to detect branching points and domain boundaries without guards. This approach isolates unhandled paths and unmet error-handling scenarios, providing structured findings for comprehensive coverage.