From edge-case-coverage
Identify and document boundary conditions, error scenarios, corner cases, and validation requirements. Use when analyzing edge cases, boundary testing, corner cases, error scenarios, validation rules, or defensive programming. NOT for writing tests (use testing-framework or test-driven-development).
How this skill is triggered — by the user, by Claude, or both
Slash command
/edge-case-coverage:edge-case-coverageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically identify and handle boundary conditions.
Systematically identify and handle boundary conditions.
| Category | Examples |
|---|---|
| Boundary | 0, 1, max, min, empty |
| Input | null, undefined, wrong type |
| State | uninitialized, concurrent, stale |
| Resource | timeout, no memory, disk full |
| Network | offline, slow, partial failure |
| Permission | unauthorized, expired, revoked |
Value: age
├── Below min: -1
├── At min: 0
├── Just above min: 1
├── Normal: 25
├── Just below max: 119
├── At max: 120
└── Above max: 121
Value: username
├── Empty: ""
├── Single char: "a"
├── Max length: "a" * 255
├── Over max: "a" * 256
├── Special chars: "user@#$"
└── Unicode: "user"
## Scenario: [Name]
**Trigger**: [What causes it]
**Symptoms**: [What user sees]
**Root cause**: [Why it happens]
**Prevention**: [How to avoid]
**Recovery**: [How to fix]
| Input | Valid | Empty | Null | Overflow | Malformed |
|---|---|---|---|---|---|
| Name | [x] | [x] | [x] | [x] | [x] |
| [x] | [x] | [x] | [x] | [x] | |
| Age | [x] | [x] | [x] | [x] | [x] |
npx claudepluginhub viktorbezdek/skillstack --plugin edge-case-coverageDocuments edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature to ensure comprehensive coverage during specification and QA planning.
Explores edge cases across 12 dimensions like invalid input, concurrency, and auth failures. Scores scenarios by likelihood x impact. Generates runnable tests for high-risk ones.
Identify and test boundary values for input validation. Use when designing test cases for numeric ranges, dates, and string lengths.