bmad-review-edge-case-hunter

Analyze code, specs, or diffs for unhandled edge cases.

1|Updated Feb 25, 2026

Search Tags:#code review #specification analysis #path analysis #diff inspection #edge case analysis

Ready to run

npx skills add https://github.com/thavirak-svay/rentify-backend --skill bmad-review-edge-case-hunter-thavirak-svay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-review-edge-case-hunter
Source: https://github.com/thavirak-svay/rentify-backend/tree/main/_bmad/core/skills/bmad-review-edge-case-hunter
Command: npx skills add https://github.com/thavirak-svay/rentify-backend --skill bmad-review-edge-case-hunter-thavirak-svay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a thorough analysis of code, specifications, or diffs to identify and report unhandled edge cases, ensuring thorough review and potential security vulnerabilities are not overlooked.

Core Features & Use Cases

Edge Case Analysis: Walks through every branching path and boundary condition to report unhandled edge cases.
Method-Driven Review: Focuses on the process and does not editorialize, reporting only unhandled paths.
Content Scope Flexibility: Analyzes diffs, full files, or functions based on the provided content.
Use Case: Ideal for reviewing code changes or specifications to ensure all potential edge cases are handled.

Quick Start

Run the 'bmad-review-edge-case-hunter' skill on the provided code diff to find 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?▼

You can find unhandled edge cases in a code diff by running an edge case analysis that walks through every branching path and boundary condition. This process reports only unhandled paths without editorializing.

What is the best way to analyze specifications for boundary conditions?▼

Analyzing specifications for boundary conditions involves a method-driven review that walks through all potential paths. This ensures thorough review and verifies that potential security vulnerabilities are not overlooked.

Can I review full files or do I need to provide a diff for edge case analysis?▼

You can analyze diffs, full files, or functions based on the provided content. The edge case analysis scope flexibly adjusts to inspect whatever content you supply.

Does this edge case analysis require external libraries for path analysis?▼

No, this edge case analysis requires no external libraries for path analysis. It independently walks through branching paths and boundary conditions to report unhandled scenarios.

How do I identify potential security vulnerabilities during a code review?▼

You identify potential security vulnerabilities during a code review by performing a comprehensive edge case analysis. This method walks through all boundary conditions to ensure potential vulnerabilities are not overlooked.

When do I need to run a method-driven review for unhandled paths?▼

You need a method-driven review for unhandled paths when reviewing code changes or specifications. It focuses strictly on the process to report unhandled paths without editorializing.