Search

PythonReactSEOPDF

documentation testing AI Skills

Discover documentation testing skills, compare source repositories and read the instructions for each workflow.

Categories: documentation testing

Showing 4,273–4,296 of 4,461

documentation testing Clear filters

Browse skills

GitHub

forge-fuzz-testing

cyotee

Property-based testing with Foundry's fuzzer. Use when writing fuzz tests, invariant tests, or testing edge cases. Covers fuzz test structure, input constraints, fixtures, and invariant testing patterns.

GitHub

java-test-engineer

peterstorm

This skill should be used when the user asks to 'write unit tests', 'add integration tests', 'create property-based tests', 'fix failing test', 'improve test coverage', 'reduce mocking', 'test this class', 'add...

GitHub

nestjs-testing

MTES-MCT

Creates unit and e2e tests for NestJS applications using Jest and Supertest. Includes patterns for testing services, controllers, guards, and e2e tests with testcontainers.

GitHub

strategy

chandima

Testing philosophy, patterns, and quality metrics. Covers the testing pyramid, test design patterns (AAA, BDD, fixtures, factories), edge case checklists, and debugging flaky tests.

GitHub

e2e-testing

TakumiOkayasu

E2Eテスト設計・実装。クリティカルパス検証とユーザージャーニー保証。

GitHub

service-test-with-dbunit

t0k0sh1

Create unit tests for Service classes using DBUnit and Spring Test DBUnit. Use this skill when writing integration tests for Service layer that require database setup with test data, when testing methods that i...

GitHub

unit-test-suite

jonathanhollander

Use this agent to create comprehensive unit test suites for backend and frontend. User: "Add unit tests for the auth module" Agent: Use unit-test-suite to create tests User: "Improve test coverage" Agent:...

GitHub

test-engineer

LPDigital-Agent

Full-stack testing specialist for Faiston NEXO. Use when writing tests, fixing test failures, or validating behaviors across Frontend (Vitest, RTL, MSW), Backend (pytest, FastAPI), and Agents (Google ADK mockin...

GitHub

testing-patterns

PhantasticUniverse

TDD, mocking, and test structure patterns. Use when writing tests, implementing TDD, creating mocks, or discussing test coverage and testing strategies.

GitHub

simulation-invariant-auditor

Hawi254

Proactively audits simulation logic while coding by collecting real artifacts via terminal access, generating helper scripts for repetitive workflows, and validating deterministic invariants across ticks, event...

GitHub

java-testing-integration

HZeroxium

Design and implement deterministic integration tests (DB/queue/external IO) using Testcontainers-style thinking, with a fixture strategy and CI-friendly execution. Use when IO/DB bugs, wiring issues, or product...

GitHub

testing-patterns

MGPowerlytics

Guidelines for testing the application, including directory structure, coverage requirements, mocking external APIs, and validation tests.

GitHub

forge-testing

cyotee

Write and run Solidity tests with Foundry. Use when writing unit tests, integration tests, or debugging test failures. Covers test structure, assertions, cheatcodes, and running tests with forge test.

GitHub

playwright-run

y047aka

Run this project's existing Playwright test suite in app/tests/. Use for running committed tests, updating snapshots, or CI validation. NOT for writing new tests or ad-hoc browser automation.

GitHub

x07-test

x07lang

Run project tests using the X07 test harness (x07 test), producing a machine-readable JSON report.

GitHub

dotnet-test-triage

bravellian

Run dotnet test, capture failed test cases, and generate a rerun filter plus a markdown failure summary. Use when test runs fail and you need a focused rerun command or a compact failure report.

GitHub

testing

Andrew1326

Testing patterns for game client and server. Auto-applies when working with tests or implementing features that need testing.

GitHub

test-driven-development

JohnStrunk

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 behavior by requiring failure fir...

GitHub

investigate

matthew-plusprogramming

Investigate connection points between specs, atomic specs, and master specs. Surface inconsistencies in env vars, APIs, data shapes, and deployment assumptions before implementation.

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.

More filters

Popularity

Popular tags