skills.rest
WritzProtocol
WritzProtocolOFFICIAL
Explore all skills by this author →
GitHub

review-edge-case-hunter

Identify unhandled edge cases in code, specs, or diffs.

3|Updated Jun 23, 2026
Search Tags:#diff analysis#code review#bug detection#path analysis#edge case analysis
One-click install
npx skills add https://github.com/WritzProtocol/writz --skill review-edge-case-hunter-writzprotocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-edge-case-hunter
Source: https://github.com/WritzProtocol/writz/tree/main/.agents/skills/review-edge-case-hunter
Command: npx skills add https://github.com/WritzProtocol/writz --skill review-edge-case-hunter-writzprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill systematically identifies unhandled edge cases in code, specs, or diffs, ensuring comprehensive coverage and reducing potential bugs.

Core Features & Use Cases

  • Exhaustive Path Analysis: Walks through all branching paths and boundary conditions.
  • Diff, File, or Function Review: Analyzes provided content regardless of type.
  • Optional Considerations: Incorporates additional areas for review if specified.
  • Output Format: Presents findings in a structured JSON array.

Quick Start

Run the review-edge-case-hunter skill on your code to automatically detect unhandled edge cases.

Frequently Asked Questions about 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?▼

To find unhandled edge cases in a code diff, you can run an automated edge case analysis on the diff content. This identifies unhandled boundary conditions and branching paths, outputting findings in a structured JSON format.

What is edge case analysis and how does it detect bugs in source code?▼

Edge case analysis is a code review technique that walks through all branching paths and boundary conditions in source code. It detects potential bugs by systematically identifying unhandled scenarios in functions or full files.

Can I review a single function for boundary conditions instead of a full file?▼

Yes, edge case analysis can operate on a single function, a full file, or a diff. You can provide just the function content to review its specific boundary conditions without analyzing the entire codebase.

How do I add specific areas of concern to an automated edge case review?▼

You can include optional additional areas for review when running edge case analysis. This allows you to specify custom considerations alongside the automated path analysis to ensure comprehensive bug detection.

What is the best way to structure edge case findings for automated tracking?▼

The best way to structure edge case findings is using a structured JSON array. This format presents unhandled edge cases systematically, allowing automated tracking systems to parse and process the detected bugs efficiently.

Does automated edge case analysis work on technical specs or only source code?▼

Automated edge case analysis works on both source code and technical specs. It systematically identifies unhandled edge cases in specs or diffs, ensuring comprehensive coverage and reducing potential bugs across different content types.

Related Skills

Explore More Software Engineering Skills→
Yukine5377Yukine5377

bmad-review-edge-case-hunter

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

Community
Advanced
AtharvaN16AtharvaN16

wayfinder

Create shared investigation ticket maps on issue trackers for project management.

Community
Advanced
beratcelik1beratcelik1
1

python-testing

Apply pytest strategies for unit, integration, async, and database tests.

Community
Intermediate
clovernguyen1010-ship-itclovernguyen1010-ship-it

bmad-review-edge-case-hunter

Identify unhandled edge cases by exhaustive path analysis of code or diffs.

Community
Advanced