test
Installation
SKILL.md
Test
Write or strengthen tests for a named behavior. Use existing tests directly when the task is only to run a known suite; this skill is not a required wrapper. A test is useful when it distinguishes an accepted outcome from a plausible failure, not merely when it executes the implementation.
Modes
| Mode | Use when | Result |
|---|---|---|
generate |
Existing behavior needs tests | Useful tests and focused/suite results |
coverage |
The caller asks to find or fill gaps | Before/after coverage, valuable tests and remaining risks |
tdd |
New behavior is being developed test first | Real expected RED, implementation, green and refactor |
strategy |
The caller wants test design only | Prioritized risks and proposed checks in the existing discussion |
Default to generate; mode and scope are skill prompt choices, not invented
CLI flags. Coverage thresholds come from the caller or repository.