QA Engineering

29

omer-metin

World-class QA engineering — systematic testing, automation, and the mindset that finds bugs before users do. Use when "QA, quality assurance, testing, test automation, e2e tests, integration tests, regression testing, test coverage, Playwright, Cypress, Selenium, test suite, bug report, test strategy, flaky tests, testing, QA, automation, e2e, integration, regression, quality" mentioned.

test-strategist

29

omer-metin

Testing strategy and design - what to test, how to test, and when testing is overkill. From TDD to integration tests to knowing when to skip tests entirelyUse when "test, testing, unit test, integration test, e2e, TDD, test coverage, how to test, should I test, test pyramid, flaky test, testing, tdd, unit-tests, integration, e2e, test-pyramid, coverage, quality" mentioned.

test-architect

29

omer-metin

Testing strategy specialist for test pyramid design, test isolation, property-based testing, and quality gatesUse when "testing, test strategy, unit test, integration test, e2e, property testing, test pyramid, flaky test, test coverage, quality gate, testing, pytest, jest, unit-testing, integration-testing, e2e, property-testing, tdd, quality, ml-memory" mentioned.

testing-automation

29

omer-metin

World-class test automation - unit, integration, e2e testing strategies, and the battle scars from flaky tests that broke CI/CD pipelinesUse when "test, testing, unit test, integration test, e2e, end to end, jest, vitest, pytest, playwright, cypress, mock, stub, fixture, coverage, tdd, bdd, flaky, test automation, testing, unit-tests, integration-tests, e2e, tdd, bdd, jest, pytest, playwright, cypress, vitest" mentioned.

playwright-testing

27

Klimabevaegelsen

Activates when writing E2E tests, debugging test failures, or working with Playwright. Use this skill for: writing test cases, using data-testid selectors, handling async operations, mocking API responses, running tests in different modes, and debugging flaky tests. Keywords: test, playwright, e2e, spec, expect, locator, data-testid, assertion

testing

27

cosmix

Comprehensive test implementation across all domains including unit, integration, e2e, security, infrastructure, data pipelines, and ML models. Covers TDD/BDD workflows, test architecture, flaky test debugging, and coverage analysis.

frontend-testing

25

chongdashu

Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y. Use for Playwright/Cypress/Vitest/Jest/RTL, flaky test triage, CI stabilization, and canvas/WebGL games (Phaser) needing deterministic input + screenshot/state assertions.

test-engineer

16

jorijn

Test planning, writing, and review across unit/integration/e2e, primarily with pytest. Use when adding tests, improving coverage, diagnosing flaky tests, or designing a testing strategy.

bats

16

OleksandrKucherenko

Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.

oberprompt

15

ryanthedev

Prompt engineering with two modes. FIX mode (default) silently improves prompts. REVIEW mode analyzes prompts verbosely. Use when writing prompts, fixing flaky prompts, or reviewing prompt quality. Triggers on "fix prompt", "improve prompt", "review prompt", "analyze prompt", "prompt engineering", "prompt not working", "flaky outputs".

flaky-tests

14

kvet

Identify flaky tests by running tests multiple times and analyzing intermittent failures. Use when investigating test reliability.

e2e-testing-standards

13

williamzujkowski

Implement robust E2E tests with Playwright or Cypress using Page Object Model, proper waits, and CI/CD integration. Covers selector strategies, flaky test prevention, and cross-browser testing patterns.

Flaky Test Detective

12

patricio0312rev

Diagnoses and fixes flaky tests by identifying root causes (timing issues, shared state, randomness, network dependencies) and provides stabilization strategies. Use for "flaky tests", "test stability", "intermittent failures", or "test debugging".

condition-based-waiting

12

hamr0

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

E2E Testing

11

mhylle

Comprehensive E2E testing skill using Playwright MCP for systematic web application testing. This skill should be used when users need to test web-based systems end-to-end, set up test regimes, run exploratory tests, or analyze test history. Triggers on requests like "test my webapp", "set up E2E tests", "run the tests", "what's been flaky", or when validating web application functionality. The skill observes and reports only - it never fixes issues. Supports three modes - setup (create test regime), run (execute tests), and report (analyze results).

e2e-testing-patterns

11

thapaliyabikendra

Master end-to-end testing with Playwright to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

cargo-nextest

10

laurigates

Next-generation test runner for Rust with parallel execution, advanced filtering, and CI integration. Use when running tests, configuring test execution, setting up CI pipelines, or optimizing test performance. Trigger terms: nextest, test runner, parallel tests, test filtering, test performance, flaky tests, CI testing.

systematic-debugging

10

alexanderop

Systematic debugging framework for any bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Triggers: "bug", "test failure", "flaky test", "debugging", "root cause", "investigate", "why is this failing", "unexpected behavior", "not working", "broken", "error", "fix this", "what's wrong".

using-quality-engineering

10

tachyon-beep

Use when a user asks about E2E testing, performance testing, chaos engineering, test automation, flaky tests, test data management, or quality practices — routes to specialist reference sheets with deep expertise rather than providing general guidance.

test-quality-analysis

10

laurigates

Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.

role-qa-engineer

9

ilandahan

QA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.

Radar

8

simota

Add edge-case tests, fix flaky tests, and improve coverage. Use when you need to address missing tests, increase reliability, or add regression tests. Multi-language support (JS/TS, Python, Go, Rust, Java).

browser-automation

5

agent-skills-hub

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202

e2e-testing-patterns

5

amurata

Master end-to-end testing with Playwright and Cypress to catch bugs, improve reliability, and enable fast deployments by building robust test suites. Use this when implementing E2E tests, debugging flaky tests, and establishing test standards.

e2e-testing-patterns

5

agent-skills-hub

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

condition-based-waiting

4

alexsandrocruz

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

playwright-expert

4

ngxtm

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing.

barrier-concurrency-testing

4

apankov1

Deterministic race condition testing using barriers and deferred promises. Replaces flaky setTimeout-based timing tests with reproducible interleaving control.

browser-automation

4

ngxtm

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...

e2e-testing-patterns

4

ngxtm

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...

chrome-devtools-debug-companion

2

graysurf

Use the chrome-devtools MCP server as a debugging companion to Playwright for browser-specific root-cause analysis (console, network, rendering, storage, and performance). Use when Playwright exposes a failure or flaky behavior and deeper Chrome runtime inspection is needed.

debugging

2

iliaal

Systematic root-cause debugging: reproduce, investigate, hypothesize, fix with verification. Use when asked to "debug this", "fix this bug", "why is this failing", "troubleshoot", or mentions errors, stack traces, broken tests, flaky tests, regressions, or unexpected behavior.

ci-analysis

1

lewing

Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed from one repo to another, reviewing code changes for correctness or style.

axiom-ios-testing

1

megastep

Use when writing ANY test, debugging flaky tests, making tests faster, or asking about Swift Testing vs XCTest. Covers unit tests, UI tests, fast tests without simulator, async testing, test architecture.

e2e-testing-patterns

1

rootcastleco

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...

axiom-ui-testing

1

megastep

Use when writing UI tests, recording interactions, tests have race conditions, timing dependencies, inconsistent pass/fail behavior, or XCTest UI tests are flaky - covers Recording UI Automation (WWDC 2025), condition-based waiting, network conditioning, multi-factor testing, crash debugging, and accessibility-first testing patterns

cpp-testing

1

gocronx

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

e2e-testing

1

gocronx

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

tracking-regression-tests

1

agent-arc-744

This skill enables Claude to track and run regression tests, ensuring new changes don't break existing functionality. It is triggered when the user asks to "track regression", "run regression tests", or uses the shortcut "reg". The skill helps in maintaining code stability by identifying critical tests, automating their execution, and analyzing the impact of changes. It also provides insights into test history and identifies flaky tests. The skill uses the `regression-test-tracker` plugin.

browser-automation

1

rootcastleco

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...

e2e-testing-patterns

1

mattmre

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

dotnet-test-quality

1

wshaddix

Measuring test effectiveness. Coverlet code coverage, Stryker.NET mutation testing, flaky detection.

systematic-debugging

1

101mare

Structured 4-phase debugging: Reproduce, Isolate, Root-Cause, Fix+Defend. Use when tracking bugs, diagnosing failures, or investigating unexpected behavior. Recognizes: "systematic-debugging", "debug this", "why does this fail", "find the bug", "track down", "root cause", "investigate error", "unexpected behavior", "it works sometimes", "flaky test"

E2E Testing Patterns

JuanJoseGonGi

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

e2e-testing-patterns

haniakrim21

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

e2e-testing-patterns

reikiplanet

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing test standards for release pipelines...

e2e-testing-patterns

oki3505F

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

playwright-expert

ARazaAnjum

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing.