Discover tools testing skills, compare source repositories and read the instructions for each workflow.
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.
Browser automation via Playwright MCP. Use for verification, browsing, web scraping, testing, screenshots, and all browser interactions.
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.
Execute comprehensive end-to-end tests for the Meal Planner application using Claude in Chrome browser automation. Supports regression testing (checklist-based) and exploratory testing (discovery-focused). Use...
Workflow for propagating penguiflow library changes to test agents. Use when modifying library code and need to test changes in test_generation agents.
Expert guide for Test-Driven Development in FastAPI, focusing on the "Quads" strategy and async testing patterns.
How to structure applications for optimal testability in Clojure and Clojurescript, along with how to use guardrails and fulcro-spec to do the actual testing. You MUST use this skill when writing Clojure and Cl...
Guide for writing tests using Fulcro Spec including specifications, assertions, mocking with when-mocking!, spying, and log capture. Use when writing or understanding tests in this codebase.
Automatically diagnose and fix failing tests by analyzing errors, updating assertions, and refactoring test code
iOS application testing and debugging using Xcode simulators for development and QA workflows
테스트 실행 및 품질 검증. Use when: (1) 테스트 실행 요청, (2) 변경 후 검증 필요, (3) 커버리지 확인.
QA 테스트 요청 스킬. Use when (1) 태스크카드 테스트 요청, (2) QA 담당자 할당, (3) 테스트 범위 지정, (4) Slack 알림 전송.
QA 테스트 관리 스킬. Use when (1) 할당된 테스트 목록 확인, (2) 테스트 결과 업데이트, (3) 테스트 완료 보고.
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.