Enumerate branching paths to expose unguarded edge cases in code.
npx skills add https://github.com/InNoobWeTrust/dotfiles --skill edge-case-hunter
Please help me install this Agent Skill. Skill: edge-case-hunter Source: https://github.com/InNoobWeTrust/dotfiles/tree/main/.agents/skills/edge-case-hunter Command: npx skills add https://github.com/InNoobWeTrust/dotfiles --skill edge-case-hunter
Mechanical edge-case and boundary-condition finder for code, diffs, specs, and logic. Use this skill whenever reviewing code for unhandled paths, testing boundary conditions, auditing branching logic, or complementing an adversarial review with method-driven path tracing. Also activate when the user says "find edge cases", "what did I miss", "boundary conditions", "unhandled paths", "off-by-one", "race condition", "null check", "missing validation", "what breaks", "what happens if", or "unhappy path". Activate proactively alongside adversarial-reviewer — they are orthogonal (attitude-driven vs method-driven) and produce different findings. Always activate when reviewing code before shipping, especially for parsers, state machines, validators, and auth flows.
Execute edge-case-hunter during code review to systematically enumerate all branching paths and surface unguarded edge cases.
High-intent search queries and answers about installing and using this skill.
To find unhandled paths during code review, systematically enumerate all branching paths across conditionals, switches, and loops to expose unguarded edge cases like missing else or default branches.
Common boundary conditions in branching logic include off-by-one errors, unguarded inputs, null checks, missing validations, and race conditions. Path tracing derives these edge classes to guide reviews.
Tracing unhappy paths in state machines or parsers requires enumerating branching paths to surface boundary conditions and missing validations. You must apply explicit guards and tests to validate coverage.
Method-driven path tracing systematically enumerates branching paths to expose unguarded edge cases, whereas adversarial review is attitude-driven. They are orthogonal approaches that produce different findings.
Audit branching logic for race conditions and off-by-one errors when reviewing code before shipping, especially for parsers, state machines, validators, and auth flows to ensure boundary conditions are handled.
amitmishra-bylddEnumerate unhandled edge-case paths in code diffs, files, or functions.
OutlineDrivenWrite adversarial tests that violate assumptions and expose failure paths.
gaiastudio-aiIdentify flaws, gaps, and risks in documents, designs, or code.
sidtheoneEnumerate code paths to identify unhandled edge cases and missing guard clauses.
