vibe-testlisted

Blast-radius-aware test generation for vibe-* projects. Traces every file a change touches, maps the full dependency graph, and writes complete test coverage across the entire blast radius — component tests, integration tests, and E2E tests. Extends existing tests in-place. Writes from scratch where none exist. Triggers on "test:" prefix, "write tests for", "test this feature", "add test coverage", "what needs testing", "test the blast radius", "coverage is missing", "write regression tests". Runs automatically at the end of vibe-add-feature and vibe-fix-bug sessions. Always use when any code has changed and test coverage must be verified or created. Never skips files. Never assumes untouched means unaffected.
aakashdhar/vibe-skill · ★ 7 · Testing & QA · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Test Skill Blast-radius-aware test generation. Traces the full dependency graph of any change, maps every affected file, and writes complete coverage — component, integration, and E2E. No gaps. No assumptions. Everything the change could have touched gets tested. **Runs in agent mode (Claude Code / Cursor). Requires filesystem access.** --- ## The principle this enforces A change is only complete when everything it could affect is verified. Direct changes are obvious. Indirect consumers are where regressions hide. This skill does not ask "what should I test?" It asks "what could this break?" — then tests all of it. --- ## Entry points ### Entry point A — On demand Triggered by: `test:`, "write tests for X", "test this feature", "coverage is missing" The user specifies what changed or what to test. Go to **Step 1 — Identify the change set**. ### Entry point B — After vibe-add-feature Triggered automatically at the end of a `feature:` session. The change set is already known: every file listed in `FEATURE_TASKS.md` under **Touches**. Skip Step 1. Read those files directly as the seed set. Go to **Step 2 — Blast radius trace**. ### Entry point C — After vibe-fix-bug Triggered automatically at the end of a `bug:` session. The change set is already known: every file listed in `BUG_TASKS.md` under **Touches**. The regression test written during `fix-bug` already exists — do not duplicate it. Note it, include it in the coverage map, skip re-writing it. Go to **S