trace-requirements
Use to trace requirements through implementation. Maps acceptance criteria to code and tests.
Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Use to trace requirements through implementation. Maps acceptance criteria to code and tests.
Use to validate reported issues. Confirms reproducibility and documents validation evidence.
Use to design test strategies and create test specifications. Documents testing approaches for stories.
Use to create QA task documents. Generates test specifications and validation requirements for QA team.
Use to create failing tests before implementing features (TDD approach). Ensures test-first development workflow.
Use to assess non-functional requirements (security, performance, reliability, maintainability) through E2E integration testing patterns.
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
Testing suite with benchmarking for version-to-version performance comparison
Generates unit tests and integration tests for Python code using pytest conventions. Use when creating tests for new functions, classes, or modules.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check...
Testing patterns and requirements for Claude Family projects
Audit code for bugs, logic errors, race conditions, and edge cases. Read-only analysis producing actionable report. Use before PR, after implementation, or when debugging. Triggers: review bugs, find bugs, chec...
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, tes...
Audit code for testability design patterns. Identifies business logic entangled with IO, hard-coded dependencies, and mocking friction. Suggests functional core / imperative shell separation. Read-only analysis...
Use when writing tests for NestJS + MikroORM with transaction rollback and real DB integration.
Generate comprehensive unit, integration, and E2E tests with edge cases, mocks, and assertions. Use when writing tests for functions, classes, APIs, or implementing TDD.
Create and manage Azure Test Plans including test cases, suites, and execution. Use when setting up test plans or managing QA processes.
This skill should be used when the user mentions "test javascript", "bun test", "unit test", "happy-dom", "test client-side js", "dom mocking", "browser tests", "test theme toggle", "test scroll handlers", or a...
Use when writing or modifying tests, fixing bugs with TDD, reviewing test code. Triggers on "test", "tests", "testing", "TDD", "test-driven", "pytest", "add tests", "write tests", "unit test", "integration test...
Python testing best practices with pytest, TDD, and mocking. ALWAYS use this skill BEFORE writing or modifying any test code. Triggers on "test", "tests", "testing", "TDD", "test-driven", "pytest", "add tests",...
Use when writing or modifying tests, fixing bugs with TDD, reviewing test code, or when user mentions "test", "tests", "testing", "TDD", "test-driven", "pytest", "add tests", "write tests", "unit test", "integr...
Tiered testing strategy (UI mock, auth stub, full-stack), fixtures, mocks, and test configuration. Handles test setup, Playwright E2E tests, pytest backend tests, mocking strategies, and CI test configuration....
Use when capturing screenshots, automating browser interactions, or scraping web content. Covers Playwright Python API for page navigation, screenshots, element selection, form filling, and waiting strategies.
Run comprehensive live API tests against Honeycomb. Manages test environments, validates documentation snippets, and tests CRUD operations. Use when you need to verify the SDK against the real API.
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.