evo-review-edge-case-hunter

Trace branching paths and boundary conditions to report unhandled edge cases.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-review-edge-case-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evo-review-edge-case-hunter
Source: https://github.com/DavidsonGomes/claude_cowork_workspace/tree/main/.claude/skills/evo-review-edge-case-hunter
Command: npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-review-edge-case-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies unhandled edge cases in content by exhaustively tracing all branching paths and boundary conditions and reporting gaps.

Core Features & Use Cases

  • Exhaustive path enumeration to surface missing guards on inputs and outputs.
  • Works with full content or diffs to reveal reachable edge cases from changed lines.
  • Useful for review workflows where precise guard coverage is required for safety.

Quick Start

Provide a content diff or full code snippet to be analyzed and output all unhandled edge-case paths.

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

Exhaustive path tracing reveals unhandled edge cases by enumerating all branching paths and boundary conditions from a code diff. It highlights gaps lacking explicit guards to ensure precise coverage in content review workflows.

What is exhaustive path tracing for input validation?

Exhaustive path tracing for input validation is a technique that enumerates all reachable branching paths to identify missing boundary condition guards. It surfaces gaps where inputs or outputs lack explicit protection against unexpected states.

How do I review code for missing guardrails and boundary conditions?

Review code for missing guardrails by exhaustively tracing all branching paths to identify gaps lacking explicit input validation. This approach highlights unhandled edge cases reachable from the provided content or diffs.

Can I use diff analysis to find reachable edge cases from changed lines?

Yes, diff analysis can find reachable edge cases by applying a deterministic scanning mindset to the changed lines. It traces the branching paths introduced by the diff to highlight gaps lacking explicit guards.

What are the limitations of automated edge case detection?

A key limitation of automated edge case detection is the potential for false positives, which requires strict step execution order and guardrails to prevent. It relies on a deterministic diff-scanning mindset to accurately report missing input validation gaps.