Test a playable browser game end to end with deterministic fixtures and real browser evidence. Use for gameplay QA, regression testing, controls, accessibility, responsive/mobile…
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…
Run the plugin's behavioral test scenarios (plugin-tests/scenarios/) against fresh subagents on hermetic throwaway boards, assert on resulting board state, and report a pass/fail…
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…
Use for property-based and stateful tests — hypothesis, proptest, fast-check, generators, shrinking.
Test runner conventions — node:test only (no Jest/Mocha), no-shrink rule on test count, mandatory failure-branch coverage for new exports, smoke tests required.
Audit a project's test suite for redundant, trivial, or mock-theater tests; relocate the ones that are the only coverage for a behavior; delete the rest.
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 一人社長,…
Test quality bar for this repo. Read when writing, reviewing, or designing tests — covers naming, abstraction level, assertions, determinism, and the process for agent-driven test…
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…
Manually dispatch and iterate on the Release Canary workflow that smoke-tests published OpenShell artifacts (install.sh on macOS/Ubuntu/Fedora, Helm chart on kind) after each…
Fix failing Vanta compliance tests using code. Apply when the user mentions Vanta tests, compliance test failures, remediation, test IDs (e.g., "cloudtrail-log-file-validation"),…
When renaming a function, test files have references that survive find-and-replace:
Building test reporting dashboards with real-time execution metrics, trend analysis, flaky test detection, coverage visualization, and integration with Allure, ReportPortal, and…
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/.
Shared rules for test runs that drive the running app or run a test target: isolation from concurrent runs, stubs for infrastructure that cannot be stood up, provisioning…
전체 또는 지정 범위의 테스트 스위트를 실행하고, 실패를 회귀·플래키·스펙불일치·환경 범주로 분류해 원인 추정과 수정안을 리포트한다. 테스트 출력은 대용량이므로 context-mode로 실행해 실패만 surface한다.
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.
Derive high-level test scenarios from a requirement or acceptance criteria before anyone writes detailed steps.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Writes and runs tests (unit, integration, E2E), performs linting, and auto-fixes failures
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 docume — from…
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,…
Comprehensive test strategy design methodology covering risk-based testing, test pyramid optimization, coverage planning, environment strategy, data management, and test…
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…
Use when the main question is whether current verification is sufficient for a change, which test layers are missing, and where the smallest high-value regression protection…
Planification de stratégie de test incluant la pyramide de tests, les quadrants de tests, la couverture et l'analyse de risques.
Assess verification scope, regression protection, and risk-based test coverage for changes under review or implementation.
For data structure validation: test lengths, relationships, constraints that must hold, verify setup is correct.
Set up testing infrastructure including framework selection, directory organization, configuration files, and initial test scaffolding. Use when starting a.
Test style rules and the flaky-test red-flag catalog — behavior-not-implementation, DAMP setup, narrow assertions, deterministic-input rules (clock, randomness, ordering, hermetic…
Analyze and score test coverage across all testing dimensions -- unit, integration, E2E, load, visual regression, contract, and accessibility.
Use when when you need to verify that a research software package (e.g., MassQL) maintains functional correctness over time, assess the reliability of a tool before integration…
Optimizing test suite execution speed with parallelization, test splitting, caching, selective test execution, and test impact analysis.
Order and prioritize test suites for faster CI feedback using failure history analysis, code change correlation, coverage-based prioritization, risk-based.
Composite skill — three-phase test quality pipeline. Chains test-health (assess state) → test-cleanup (remove redundant/brittle tests) → mutation-test (validate surviving suite).
Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.
Analyzes test suites and tags each test with a standardized set of traits (e.g., positive, negative, critical-path, boundary, smoke, regression).
Execute a test scenario against a team, observing coordination pattern behaviors, evaluating acceptance criteria, and generating a structured RESULT.md.
Use before scaling any message, after a launch underperforms, or whenever positioning is still a hypothesis (pre-users).