Security & Testing Agent Skills

Walk one test-driven development cycle (RED then GREEN, optionally Refactor while GREEN).

Designs, implements, and refines automated test suites across multiple frameworks with deterministic isolation and behavior-focused…

Investigates failing tests and routes the issue to the right developer using dependency and history context.

Initialize test framework with Playwright or Cypress.

Performs pseudo-mutation analysis on .NET production code to find gaps in existing test suites.

Detect missing test coverage and generate test suggestions.

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect…

Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for…

Test a playable browser game end to end with deterministic fixtures and real browser evidence.

Generate test outlines (living documentation) and test code from natural language feature descriptions.

Launch, retain, and test the T3 Code web app in isolated development environments, including first-try browser authentication with…

Guide for testing Codex TUI interactively

Verify working-tree changes against an 8-tier test pyramid.

Generate AscendC testcases that hit intended implementation semantics.

After code changes, run the required baseline (moon tasks run from anywhere in the repo, including CI-marked agent shells): Useful…

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior…

Use when the user wants to audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration.

Unit testing, integration testing, and test-driven development principles.

Automatically generates comprehensive test suites (unit, integration, E2E) based on code and past testing patterns.

Testing code that calls an APIMatic-generated .NET SDK in C# — which seam to fake, covering error and edge paths, asserting real behaviour…

How to write integration tests for error processors in packages/core/src/processors/.