Test implementation patterns and conventions. Use when implementing unit tests, integration tests, or E2E tests, including RTL+Vitest+MSW component testing and Playwright E2E…
Patterns and conventions for writing *.integration.test.ts files. Covers DI stub strategy (infra-layer only), file placement, mock setup, and Vitest isolation requirements.
Phase 1 of the test-readiness pipeline. Crawls a target repo, classifies every meaningful unit of code (business logic, service boundary, HTTP route, error path, external…
Make tests order-independent by resetting state, banning shared globals, and giving each worker its own resources.
Use when assessing the founder's ceiling — can they paint the huge future AND walk the exact next step, and do they bend reality or wait for permission.
व्यवहार, APIs, snapshots, compatibility, या bug fix बदलावों के अनुसार परीक्षण जोड़ने, अपडेट करने, हटाने, या ऑडिट करने के समय इस स्किल का उपयोग करें।
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, perfor — from…
Phase 3 of the test-readiness pipeline. Reconciles existing tests against the Phase 1 inventory and Phase 2 blueprint, bucketing each existing test and each inventory item into…
Add focused deterministic tests, fixtures, golden examples, or smoke checks for workflows that can run while still being wrong.
Mutation testing workflow. Systematically mutates source code to verify tests actually catch bugs. Multi-session with progress tracking.
Ensure tests use clear naming and cover edge cases with proper describe/it structure.
Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category.
Testování otázek z databáze českého občanství. Náhodně vybírá otázky, zobrazuje možnosti A-D, čeká na odpověď uživatele, zobrazuje správnou odpověď a sleduje pokrok.
Coordinates testing strategy and execution across all test types. Use when creating test plans, implementing tests (unit/integration/E2E), or enforcing coverage requirements (80%…
Test Organization Helper - Auto-activating skill for Test Automation. Triggers on: test organization helper, test organization helper Part of the Test Automation skill category.
Use when you need to verify whether a GitHub Actions workflow badge (e.g., main.yml) accurately reports the CI pipeline's true pass/fail status.
Test Parallelizer - Auto-activating skill for Test Automation. Triggers on: test parallelizer, test parallelizer Part of the Test Automation skill category.
Tests whether patterns actually work — trigger, emerge, and produce value. Use when (1) user wants to verify a pattern before relying on it, (2) user runs /test-pattern command,…
Write and run tests across languages and frameworks. Use when setting up test suites, writing unit/integration/E2E tests, measuring coverage, mocking dependencies, or debugging…
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Performance test orchestrator — choose a sub-type or run the full pipeline. Requires a running environment.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Database performance test workflow — slow queries, missing indexes, and N+1 patterns via EXPLAIN ANALYZE.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Frontend performance test workflow — Core Web Vitals (LCP, CLS, INP), bundle size, and render performance.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Load test workflow — measures p95/p99 latency and throughput at expected concurrent users.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] CPU and memory profiling workflow — flamegraphs and heap snapshots to pinpoint hot paths and memory leaks.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Soak test workflow — sustained load for 30-60 min to detect memory leaks and connection pool exhaustion.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Stress test workflow — ramps load beyond capacity to find breaking point and verify recovery.
Use when optimizing test suite performance — database setup, seeder optimization, parallel testing, CI pipeline efficiency, or RefreshDatabase alternatives.
Test plan generation skill covering requirements analysis, test strategy, coverage matrices, risk-based testing, and test estimation techniques.
Close the PDCA loop on the work you just did. After implementing changes, drive the LIVE app on localhost through the Playwright browser MCP like a real end user — manually, not…
Use to restructure code while guaranteeing that all existing tests continue to pass.
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt…
Rebalance a top-heavy test suite toward fast unit tests without dropping the coverage the slow tests provide.
GENERIC webapp QA fallback — use ONLY when no project-specific QA skill applies (66ai-user-story-testing for 6-6 AI, sbc-qa-data-integrity-audit/sbc-pdca-audit for 一人社長,…
Analyze test code quality to detect coverage-only tests, test smells, and low-value assertions. Use when asked to "analyze test quality", "find coverage-only tests", "audit our…
Add, repair, and improve tests and coverage. Use when Codex needs to generate unit tests, fix failing tests, improve meaningful coverage, test error handling, add Playwright…
Orchestrates the full test-readiness pipeline (phases 1–5), once per qualifying repo under repos/, each in its own worktree + branch.
Pre-test readiness workflow that finds and fixes predictable validation blockers before running expensive local or container test gates.
Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify…
When renaming a function, test files have references that survive find-and-replace:
Make UIs responsive across all devices and verify responsiveness using Playwright. Includes scrollbar testing, breakpoint verification, and layout validation.
Use when when you need to validate that a package's periodic integration test suite (distinct from unit tests) passes as expected, or when you must collect and communicate…
Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category.
Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category.
Use when auditing tests that may not verify real behavior: tautological assertions, missing assertions, skipped tests without a tracker, mock-everything tests, swallowed…
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
Auto-detect and run project tests — supports Go, TypeScript, Python, Rust, and more
Generate test file scaffolds from source analysis with language-appropriate templates.
Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Use when writing RSpec tests for service objects, API clients, orchestrators, or business logic in spec/services/.
BATS shell script testing. Use when writing or running shell script tests. Covers setup/teardown, assertions, mocking, helper patterns, and coverage with kcov.
Test Shiny applications using shinytest2 for end-to-end browser tests and testServer() for unit-testing module server logic.
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
Deep formal test smell audit based on academic research taxonomy (testsmells.org). Detects 19 categorized smell types — conditional logic, mystery guests, sensitive equal — from…
Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan. Creates TEST_SPEC.md from PRD and implementation specs.
Keep the suite fast enough to run on every change by measuring the slow tests, shaping the pyramid, cutting IO from the fast tier, and sharding.
Test feature branches on Vercel preview deployments using Chrome automation and Gmail OTP
Testing strategy and design - what to test, how to test, and when testing is overkill. From TDD to integration tests to knowing when to skip tests entirelyUse when "test, testing,…
Designs a risk-based test strategy mapped to acceptance criteria without writing test code unless asked. Use after planning and before or during implementation.
Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing…