review-edge-case-hunter

Enumerate branching paths in code or diffs and report unhandled edge cases as JSON.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/chrissstellee/Movix --skill review-edge-case-hunter-chrissstellee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-edge-case-hunter
Source: https://github.com/chrissstellee/Movix/tree/main/.agents/skills/review-edge-case-hunter
Command: npx skills add https://github.com/chrissstellee/Movix --skill review-edge-case-hunter-chrissstellee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss boundary conditions and unguarded branches that only surface as production bugs. This Skill mechanically walks every control-flow path and domain boundary in a diff, file, or function and reports only the edge cases that lack explicit handling. ## Core Features & Use Cases - Exhaustive Path Enumeration: Walks conditionals, loops, error handlers, early returns, and domain boundaries such as off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, and timeout gaps. - Diff-Aware Scoping: When given a diff, analyzes only changed hunks and boundaries directly reachable from changed lines; when given a full file or function, treats the entire content as scope. - Structured JSON Findings: Returns a strict JSON array with location, trigger condition, guard snippet, and potential consequence for each unhandled path, with an empty array when nothing is missing. - Use Case: Paste a pull request diff before merging and receive a list of unguarded null inputs, missing else branches, and unhandled error paths with minimal guard snippets to close each gap. ## Quick Start Ask the AI to run an edge-case review on the provided diff or function and list only the unhandled boundary conditions as JSON.

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?▼

Provide the diff as the content input and the review walks every branch reachable from the changed lines. It reports only boundaries lacking an explicit guard in the diff, returned as a JSON array with location, trigger condition, guard snippet, and consequence.

What kinds of edge cases does an edge case review check?▼

The review derives edge classes from the content itself rather than a fixed checklist. Typical classes include missing else or default branches, unguarded null or empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, and timeout gaps.

Can I review a full file instead of a diff for edge cases?▼

Yes. When no diff is provided, the entire file or function becomes the analysis scope and every branching path within it is walked. Content outside the provided input is ignored unless explicitly referenced.

What output format does the edge case review return?▼

It returns only a valid JSON array where each object has exactly four fields: location, trigger_condition, guard_snippet, and potential_consequence. An empty array is returned when no unhandled paths are found, with no extra text or markdown.

When should I not use exhaustive edge case analysis?▼

It is not suited for judging code quality, style, or architecture since it deliberately never comments on whether code is good or bad. Use it specifically when you need mechanical completeness checking of branches and boundaries, not general design feedback.