skills.rest
b566776
b566776COMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Enumerate unhandled edge cases and boundary conditions from code diffs or files.

Updated May 5, 2026
Search Tags:#code-review#diff-review#edge-case#boundary-conditions#exhaustive-analysis#path-tracing#defect-detection
One-click install
npx skills add https://github.com/b566776/whitebox --skill bmad-review-edge-case-hunter-b566776
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/b566776/whitebox/tree/main/.gemini/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/b566776/whitebox --skill bmad-review-edge-case-hunter-b566776

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exhaustively enumerates edge cases and boundary conditions from code content.

Core Features & Use Cases

  • Exhaustive path enumeration of branching logic in code, diffs, or specs.
  • Reports only unhandled paths, avoiding analysis of already-covered cases.
  • Provides deterministic, guardrail-focused findings suitable for manual review.

Quick Start

Provide the content to review (diff, full file, or function) and run the edge-case tracer 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?▼

To find unhandled edge cases in a code diff, provide the changed lines to an exhaustive path tracer. It scans the diff and enumerates only boundary conditions lacking explicit guards, ignoring already-handled cases.

What is exhaustive path tracing for boundary conditions?▼

Exhaustive path tracing is a code review technique that enumerates all branching logic paths. It identifies boundary conditions and reports only unhandled paths with explicit guards, avoiding analysis of already-covered cases.

Can I scan a full source file for missing boundary conditions?▼

Yes, you can scan a full source file for missing boundary conditions. The tracer treats the entire file content as scope, enumerating unhandled paths and defect-detection opportunities throughout the code.

How do I review code for unhandled paths and boundary logic?▼

Review code for unhandled paths by running the edge-case tracer on your content. It performs exhaustive path enumeration and provides deterministic, guardrail-focused findings suitable for manual defect detection.

Does the edge-case tracer analyze already-handled conditional paths?▼

No, the edge-case tracer does not analyze already-handled conditional paths. It strictly lists unhandled paths with explicit guards, avoiding analysis of covered cases to focus manual review on actual gaps.

Related Skills

Explore More Software Engineering Skills→
geekdesign27geekdesign27

bmad-review-edge-case-hunter

Enumerates unhandled edge cases in code, specifications, or diffs via path tracing.

Community
Advanced
curdxcurdx
4

bmad-review-edge-case-hunter

Trace branching paths and boundary conditions to find unhandled edge cases.

Community
Advanced
bitwardenbitwarden
129

reviewing-incremental-changes

Re-review only changed lines in pull requests after developer updates.

Official
Basic
peshaypeshay
1

bmad-review-edge-case-hunter

Enumerate control flow paths to identify unhandled edge cases in code, specs, or diffs.

Community
Advanced