Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkillsEngineering › Testing › Page 51

Testing (Page 51 of 66)

3955 Claude Code skills in the Testing sub-category of Engineering.

3,955 skills · updated 2026-08-26 · showing 3001–3060 of 3,955 by quality score

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Use to PRODUCE test-suite artifacts — author a new test or test plan for a feature, shape a cross-layer test strategy (what to test at which layer, as a portfolio), or plan which…
Use this agent when you need to evaluate test quality using Dave Farley's 8 properties of good tests.
Wizualne testowanie designow - ustawia kazdy design, odpala nagrywanie, robi screenshot i ocenia wyglad
Use when testing the Hubble Electron desktop app, especially when inspecting, clicking, screenshotting, or verifying a real note edit in the running app.
Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others.
Automatically detect test frameworks (Jest, pytest, RSpec, xUnit) in projects by analyzing configuration files and dependencies
Analyze, prioritize, and document test cases in TMS (Jira/Xray) -- the bridge between manual QA and test automation.
Choose stubs, fakes, and mocks deliberately and default to verifying state over interaction so tests survive refactors.
Use when designing or reviewing test doubles — the stand-in objects that replace real collaborators in a test: the five-kind taxonomy (dummy, stub, spy, fake, mock) from…
Test-Driven Development (TDD) - design tests from requirements, then execute RED -> GREEN -> REFACTOR cycle.
Test-driven bug-fix methodology — reproduce the defect first, write a failing test that captures it, then fix red-to-green. Load when fixing a bug, defect, or regression report.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks…
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior.
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 — from…
Enforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.
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 — from…
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.
Modify an existing `test` declaration -- changing its body (sends, matches, captures, fail patterns, sleeps), markers, `start` deps, `let` bindings, docstring, name, cleanup -- or…
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.
Acceptance tests as immutable scope fence — loaded by test-architect and orchestrator to enforce test-before-implementation discipline and completion contracts
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…
Find and monitor gas prices with daily notifications. Use when searching for the cheapest gas in a specific area, tracking Costco and other discount fuel stations, or set — from…
Use when generating tests for untested code — happy path, edge cases, error handling
Use when generating test files for existing code or from a spec — not for the TDD red-green-refactor loop (use tdd). Language-agnostic, works with any test framework.
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.
Design and run a k6/Artillery load profile that measures throughput, latency percentiles, error rate, and the breaking point under concurrent traffic.
व्यवहार, 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…
Render JSON schemas to images and generate schemas from prompts using declare-render and AI.
All Engineering skills →
More in EngineeringDevops (3,719) · Architecture (3,060) · Backend (2,477) · Frontend (1,674) · Languages (1,461) · Code Quality (1,434) · Cloud Platforms (1,292) · Databases (890) · Performance (843) · Mobile (630) · Observability (438) · Data Engineering (371) · Docs Engineering (319) · Workflow Orchestration (286) · ML AI Eng (280) · API Tooling (23)