skills.rest
skyoxu
skyoxuCOMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Identify unhandled edge-case paths in diffs or full files.

Updated Nov 6, 2025
Search Tags:#code-review#diff-analysis#edge-case#boundary-conditions#path-tracing#guard-conditions#exhaustive-review
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-review-edge-case-hunter-skyoxu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-review-edge-case-hunter-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables exhaustive discovery of unhandled edge-case paths in content, focusing on diffs or entire files, and reports only gaps in handling.

Core Features & Use Cases

  • Systematically enumerate branching paths and boundary conditions present in content.
  • When a diff is provided, analyze only the changed lines and their reachable states, reporting unguarded boundaries.
  • When analyzing full content, treat all content as scope and surface missing guards and edge-case guards.
  • Use cases include code review, spec analysis, and design diffs where complete edge-case coverage is essential.

Quick Start

Analyze the provided content to enumerate unhandled edge-case paths and boundaries.

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, analyze the changed lines and their reachable boundaries to report gaps with no explicit guards. This path tracing ensures exhaustive coverage of branching conditions introduced by recent modifications.

What is exhaustive edge-case path tracing in code review?▼

Exhaustive edge-case path tracing systematically enumerates all branching paths and boundary conditions in source files. It surfaces missing guard conditions to ensure complete edge-case coverage during code review or spec analysis.

Can I analyze boundary conditions in a full source file without a diff?▼

Yes, you can analyze boundary conditions in a full source file without a diff. The entire content is treated as the scope, systematically reporting any missing guards or unhandled edge-case paths present in the code.

What's the best way to identify missing guard conditions in code?▼

The best way to identify missing guard conditions is to systematically enumerate all branching paths and boundary conditions. By treating the entire content as scope, you can surface any missing guards and ensure exhaustive edge-case coverage.

Does diff analysis only check the changed lines for edge cases?▼

Yes, diff analysis checks only the changed lines and their reachable boundaries for edge cases. It specifically targets these modified states to report gaps with no explicit guards, ensuring focused and efficient code review.

Related Skills

Explore More Software Engineering Skills→
MarkusonMarkuson

bmad-review-edge-case-hunter

Trace control flow and state transitions to detect unhandled edge cases.

Community
Advanced
InNoobWeTrustInNoobWeTrust
4

edge-case-hunter

Enumerate branching paths to expose unguarded edge cases in code.

Community
Advanced
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate
Yukine5377Yukine5377

bmad-review-edge-case-hunter

Enumerate unhandled edge cases in diffs, files, or functions via exhaustive path analysis.

Community
Advanced