Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify…
Enforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.
Execute feature work and bug fixes with a tracer-bullet red-green-refactor loop. Use when building behavior that should be guided by tests, when fixing regressions, or when the…
End-to-end infrastructure pipeline validation across Terraform and Ansible repos
Use when evaluating the core insight or differentiation — test whether the "secret" is earned or faked.
Automated test validation, coverage checking, and quality metrics with aggressive defaults
Use when creating or improving RSpec test coverage for Rails engines. Covers dummy app setup, request, routing, generator, and configuration specs for proving engine beha — from…
QA and testing agent that writes unit tests, integration tests, and edge case coverage for the codebase.
Test design and authoring workflow for effective, fast, deterministic test suites. Use when writing or modifying tests, adding coverage for new or changed behavior, creating…
Use to provision test environments — real production-engine datastores (containerized), faked externals, isolated per-run state, and critical environment/config validation so…
Close the gaps between test and production by matching versions, data shape, and configuration paths so a passing suite actually predicts prod behavior.
Full testing pipeline — automated test sweep, browser/Playwright testing, dependency health audit, and manual test checklist.
Design and execute risk-based software verification that produces trustworthy evidence rather than false-green checks.
Check whether changed code paths have corresponding tests and suggest minimal coverage.
Use when you have modified the Scanpy codebase (e.g., added a feature or bugfix) and need to confirm that all unit and integration tests pass before submitting a pull request, or…
Systematically triage failing tests by grouping errors, fixing root causes in priority order, and verifying incrementally.
Read docs/test-readiness/test-readiness-plan.md and queue its flat T-NNN task list as task-store tasks, one task per row, with dependency edges (predecessor/fan-out) and per-task…
Discover Go test failures, partition by package/count, spawn N parallel test-fix-loop agents, verify results. Args:
[max-agents]
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\"fix these tests\", \"make tests pass\"), reports test…
Reusable test fixtures in tests/fixtures/*.json with declarative schema. Generated test cases feed into injection counters, redactor, and validation gates.
Cap flaky tests with a measured budget, quarantine them off the merge gate, and burn them down under named owners and deadlines.
Use when locking down user paths as E2E regression tests. Explores the actual UI in a browser, proposes user flows, writes automated E2E tests (Playwright/Cypress/etc.), and runs…
Generate comprehensive tests across all stacks — .NET, NestJS, React, React Native, Flutter
Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to…
Performs pseudo-mutation analysis on .NET production code to find gaps in existing test suites. Use when the user asks to find weak tests, discover untested edge cases, c — from…
Analyzes code to identify untested functions, low coverage areas, and missing edge cases. Use when reviewing test coverage or planning test improvements.
Review whether existing tests and verification credibly prove a scoped behavior contract. Use during validation when evidence may omit important behavior or provide false…
Use when generating tests for untested code — happy path, edge cases, error handling
Review generated or changed test code against universal testing rules before it ships or is presented for approval.
Diagnostic testing skill for verifying AgentNova's skill system, tool usage, and instruction following.
Use when reviewing, designing, triaging, or rationalizing test suites — unit, integration, e2e/UI, exploratory, property-based, contract, snapshot, mutation, or performance tests.
Design and run bounded HTTP failure-path tests with ordered retry sequences, temporary status endpoints, hash-only webhook attempt meters, and deterministic synthetic fixtures.
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] 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.