skills.rest
josemariafs
josemariafsCOMMUNITY
Explore all skills by this author →
GitHub

bmad-review-edge-case-hunter

Enumerate unhandled edge-case paths in diffs, files, or functions.

3|2|Updated Mar 29, 2024
Search Tags:#code-analysis#guardrails#diff-review#edge-case#boundary-conditions#path-tracing
One-click install
npx skills add https://github.com/josemariafs/MVTools --skill bmad-review-edge-case-hunter-josemariafs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-review-edge-case-hunter-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces exhaustive analysis by walking every branching path and boundary condition to reveal unhandled edge cases in content such as diffs or full files.

Core Features & Use Cases

  • Exhaustive path enumeration for provided diffs or code blocks.
  • Boundary-condition discovery across control flow, inputs, and state transitions.
  • Clear, actionable findings listing unhandled paths only (no editorializing). Use cases include code reviews, specification analysis, and diff auditing where completeness and guardrails matter.

Quick Start

Provide the target diff, file, or function to analyze, and the tool will 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 before merging?▼

Exhaustive path analysis identifies unhandled edge cases in code diffs by walking every branching path and boundary condition. It reveals gaps and missing guardrails for robust behavior without editorial commentary.

What is path tracing for boundary conditions in code reviews?▼

Path tracing for boundary conditions is an exhaustive analysis mechanism that walks every branching path and state transition. It identifies and reports only unhandled paths and missing guardrails during code reviews.

Can I audit full files for missing guardrails or does it only work on diffs?▼

You can audit full files, individual functions, and diffs for missing guardrails. The analysis performs exhaustive path enumeration across any provided code content to identify unhandled edge cases and missing guardrails.

What's the best way to enumerate state transition gaps during specification analysis?▼

The best way to enumerate state transition gaps is exhaustive path analysis across control flow and inputs. This approach maps every branching path to report only unhandled paths and missing guardrails.

Does the edge case analysis provide suggestions on how to fix the unhandled paths?▼

No, the edge case analysis does not provide suggestions or editorial commentary on fixing unhandled paths. It focuses exclusively on identifying and reporting gaps and guardrails for robust behavior.

Related Skills

Explore More Software Engineering Skills→
ahkohdahkohd
5

code-review

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

Community
Advanced
VYRE-StudiosVYRE-Studios

simplify

Simplify recently changed code files by fixing duplication and inefficiency.

Official
Intermediate
diegosanchespereira1diegosanchespereira1

bmad-review-edge-case-hunter

Trace control flow paths to identify unhandled edge cases in code, specs, and diffs.

Community
Advanced
Cbanzaime23Cbanzaime23

bmad-review-edge-case-hunter

Trace all branching paths in code diffs to report unhandled edge cases.

Community
Advanced