skills.rest
thuantan2060
thuantan2060COMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Enumerate branching paths and boundary conditions to detect missing guards in code.

Updated May 17, 2026
Search Tags:#code review#bug prevention#edge-case analysis#boundary conditions#path enumeration#diff scanning#guard detection
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-review-edge-case-hunter-thuantan2060
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-review-edge-case-hunter-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents missed boundary-condition bugs by forcing complete path enumeration and reporting only the unhandled conditions.

Core Features & Use Cases

  • Exhaustive path enumeration: Mechanically walks branching paths and boundary transitions in the provided scope.
  • Diff-scoped review: When given a diff, limits analysis to reachable boundaries from changed lines that lack explicit guards.
  • Actionable findings only: Outputs findings without commentary about code quality, focusing strictly on missing handling.

Quick Start

Ask the skill to review the provided diff or file content for any unhandled edge-case paths and boundary conditions.

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 and missing guards in a code review?▼

To find unhandled edge cases in a code review, exhaustively enumerate branching paths and boundary conditions to identify missing guards. This method-driven detection reports only unhandled conditions rather than subjective critique.

Can I scan only the changed lines in a diff for missing boundary conditions?▼

Yes, you can perform diff-scoped review to scan only changed lines for missing boundary conditions. The analysis limits detection to reachable boundaries from the diff that lack explicit guards, avoiding full-file processing.

What is exhaustive path enumeration for bug prevention?▼

Exhaustive path enumeration for bug prevention mechanically walks all branching paths and boundary transitions in a provided scope. It deterministically identifies missing handling logic to prevent missed boundary-condition bugs.

Does the edge-case analysis output include code quality commentary?▼

No, edge-case analysis outputs actionable findings only without code quality commentary. It focuses strictly on deterministically reporting missing handling logic for boundary conditions in a JSON-only format.

What happens if empty or undecodable input is provided to a path enumeration tool?▼

When empty or undecodable input is provided to a path enumeration tool, the process halts immediately. This ensures deterministic detection only runs on valid code content, diffs, or specs.

Related Skills

Explore More Software Engineering Skills→
ahkohdahkohd
5

code-review

Identify bugs and edge cases in code diffs with prioritized fixes.

Community
Advanced
tabesinktabesink

bmad-review-edge-case-hunter

Enumerate unhandled edge cases by path-tracing branching and boundary conditions in code or diffs.

Community
Advanced
GenEducationGenEducation

bmad-review-edge-case-hunter

Trace code paths and report missing boundary guards in diffs.

Official
Advanced
deltatreedeltatree

bmad-review-edge-case-hunter

Enumerate control flow paths and boundary conditions to report unhandled edge cases.

Community
Advanced