bmad-review-edge-case-hunter

Enumerate unhandled edge-case paths in code, diffs, or specs.

4|1|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-review-edge-case-hunter-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/core/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-review-edge-case-hunter-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security-focused reviewers enumerate all unhandled edge cases in code, diffs, or specs by ignoring general quality judgments and focusing solely on uncovered paths.

Core Features & Use Cases

  • Exhaustive path enumeration across control-flow structures (conditionals, loops, error handlers) and domain boundaries to reveal unhandled branches.
  • Strict, deterministic analysis: respects the provided scope (diffs, full files, or functions) and reports only paths not guarded in the given content.
  • Actionable findings: outputs precise, guard-gap items without editorial comments, enabling rapid remediation.

Quick Start

Provide the content to review (diff, full file, or function) and the tool will enumerate 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, provide the diff content to enumerate all uncovered control-flow paths, loops, and error handlers. The analysis strictly respects the provided scope and reports only paths missing explicit guard conditions.

What is exhaustive edge-case path analysis for code review?

Exhaustive edge-case path analysis is a deterministic review technique that traverses control-flow boundaries and domain logic to surface gaps. It outputs precise, actionable guard-gap items instead of general quality judgments, ensuring all unhandled branches are identified.

Can I use path traversal analysis on a single function scope?

Yes, you can perform path traversal analysis on a single function scope. The analysis applies to diffs, full files, or specific functions, enumerating unhandled edge cases and detecting missing guard conditions strictly within the defined content boundaries.

Does this edge-case hunter check for missing guard conditions across error handlers?

Yes, this edge-case hunter specifically checks for missing guard conditions across error handlers. It performs exhaustive path enumeration across control-flow structures to surface unhandled branches and report exact gaps without adding editorial comments.

What is the best way to enumerate unhandled paths in a full-file code review?

The best way to enumerate unhandled paths in a full-file code review is to provide the complete file for strict, deterministic analysis. This surfaces all unguarded paths across conditionals, loops, and error handlers, providing actionable findings for rapid remediation.