Stats
Actions
Tags
From test-driver
Always-on testing awareness driver. MUST consult during any implementation task to evaluate whether testing is needed at this point. Applies to every task involving code changes. Governs: when to suggest gap analysis, how to assess test coverage needs, delegation to framework-specific testing plugins, and non-intrusive suggestion cadence. Triggers on: test, implement, feature, fix, bug, refactor, build, create, modify, change, add, update, debug, complete, finish, deploy, merge, PR, commit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/test-driver:testing-mindsetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have a testing-aware mindset installed. This skill does not run tests or write tests itself; it teaches you *when* to think about testing and *what* to suggest. The actual test writing and execution is handled by the gap-analysis, convergence-loop, and test-design skills, plus framework-specific plugins.
You have a testing-aware mindset installed. This skill does not run tests or write tests itself; it teaches you when to think about testing and what to suggest. The actual test writing and execution is handled by the gap-analysis, convergence-loop, and test-design skills, plus framework-specific plugins.
Intentionally always-on. The broad trigger list ensures this skill loads for any implementation task. The cadence rules below prevent noise.
After completing any code change, ask yourself these questions:
Before suggesting a gap analysis, check these three conditions:
docs/testing/TEST_STATUS.json (if it exists) and compare the last_analysis.date against recent file modifications.Decision: If two or more conditions are true, suggest running /test-driver:analyze. If only one condition is true, note it silently and wait for the next check.
When writing tests, do not reinvent framework-specific patterns. Consult the matching plugin:
| Project Type | Consult |
|---|---|
| Python (general) | python-dev:python-testing-patterns for pytest fixtures, mocking, parametrize |
| PySide6/PyQt6 | qt-suite:qtest-patterns for widget tests, qt-suite:qt-pilot-usage for GUI testing |
| Home Assistant | home-assistant-dev:ha-testing for hass fixtures, config flow tests |
| Swift/SwiftUI | Self-contained in the swift-swiftui stack profile |
Graceful degradation: If the delegated plugin is not installed, proceed using general knowledge. The framework plugin enhances accuracy but is not required.
test-driver drives the when and what. Framework plugins provide the how.
superpowers:test-driven-development is driving the session (test-first workflow), testing-mindset defers entirely. TDD handles test-first; test-driver handles test-after and gap-filling.superpowers:verification-before-completion if it's active. Both skills care about pre-commit readiness; avoid duplicate suggestions.This skill does not:
superpowers:test-driven-development)It only drives awareness and timing for when testing should be considered.
npx claudepluginhub l3digitalnet/claude-code-plugins --plugin test-driverCreates and manages unit and integration tests by analyzing codebase, auto-detecting test frameworks, and generating tests that follow project conventions.
Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.
Consults test-architecture agent for testing strategy and design including coverage gaps, flaky tests, framework selection, test pyramid analysis, and new feature test planning.