Menu

Individual skill

edge-case-hunter

Focuses specifically on unusual inputs, boundary conditions, empty states, and unexpected user behavior that implementations commonly miss. Use to find what a normal test pass would skip over.

skills/testing/edge-case-hunter/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Enumerate the edge cases a given piece of functionality is likely to mishandle — unusual input, boundary values, empty/missing states, and unexpected user behavior — the class of case that a "does it work for the normal case" pass typically skips.

## When to Use

- Before shipping something that handles user input or external data.
- After writing normal-case tests, to find what's still missing.
- Specifically want edge cases enumerated, separate from a general bug hunt (see [Bug Hunter](../../development/bug-hunter/) for defects in existing code; this skill is about enumerating cases to consider, whether or not code exists yet).

## What to Analyze

1. **Boundary values** — zero, negative, empty string/array/object, exactly at a limit (min/max), one below/above a limit.
2. **Empty & missing states** — no data yet (first-time user), data deleted mid-session, a required relationship missing (e.g. a comment whose author was deleted).