Run, write, and debug tests — unit, integration, and end-to-end — in whatever framework the project already uses (Jest, Vitest, PHPUnit, Pytest, Go test, cargo test, RSpec, JUnit). Invoke when the user asks to test something, run the suite, add or fix tests, check coverage, or investigate a failing test. Skip when they want a code review rather than tests, or are asking how a test framework works in the abstract.
Stratégies de test, TDD, tests unitaires, d'intégration, E2E, et couverture de code. Use when writing or fixing unit, integration or E2E tests, choosing a test strategy, setting up TDD, mocks, fixtures or coverage, or when the user says test, tester, couverture, TDD, jest, vitest ou playwright.
Write comprehensive, maintainable tests following TDD and AAA pattern. Use when writing unit tests, integration tests, setting up fixtures, mocking dependencies, or improving test coverage. Covers Python (pytest), TypeScript (Jest), Go (testing), and Rust (built-in + proptest). Do NOT use for mutation testing specifics (use mutation-testing skill).
Write unit tests, integration tests, and end-to-end tests. Use when implementing test suites, improving coverage, or ensuring code quality through testing.
Use when implementing any feature or bugfix and a test-driven approach is appropriate (red-green-refactor, seams-first), or when the user asks to find testing gaps, mutation test, or identify surviving mutants. Unit and integration tests only; browser journeys go to e2e-testing, test infrastructure to observability-quality, completion claims to gates.
Test scenarios, coverage analysis, test quality standards, and the mandatory test failure stop protocol. Load this skill for any task requiring test coverage.
Use when defining a test strategy, choosing layers, raising meaningful coverage, or fixing flaky suites — write tests with the feature, failing test first for bugs, QA audit before launch.
Write and review tests at all levels — Unit, Integration/Feature, and E2E — following Martin Fowler's testing pyramid. Use this skill when creating, modifying, or reviewing any test. Prevents test bloat, fragile assertions, and misplaced test levels. Adapts to any language/framework by following the decision flowchart and layer guidelines.
Apply battle-tested strategies for unit, integration, and E2E testing in production SaaS applications. TRIGGER this skill automatically when the user mentions: writing tests, Jest, Vitest, Playwright, Cypress, test coverage, unit tests, integration tests, E2E tests, mocking, test setup, "how do I test this", TDD, testing hooks or components, testing API routes, CI test runs, or any quality assurance topic. Also trigger when new features are added without tests or when existing tests are failing unexpectedly.
Produce proportionate automated evidence for software behavior. Use when writing or selecting tests, checking a regression or requirement, investigating a test failure, or assessing whether passing tests support a claim. Compose with implementation, debugging, browser QA, and code review as needed; do not take over their workflows or require tests for every trivial reversible edit.
Testing strategy, coverage analysis, and quality assurance. Use when: (1) Planning test strategy for a story, (2) Analyzing test coverage, (3) Reviewing test quality in PRs, (4) Creating mocks for integrations, (5) Defining testing standards. Referenced by developer-analysis (test strategy in design) and git-workflow (PR review test verification).
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
cachewraithSkill
