Design CI/CD pipelines for test execution. Covers GitHub Actions and GitLab CI pipeline templates, parallelism and sharding strategies, artifact management, flaky test quarantine, test result publishing, and quality gates. Includes copy-paste-ready workflow files for Playwright, Jest, and multi-stage pipelines. Use when: "CI/CD," "GitHub Actions," "pipeline," "test in CI," "GitLab CI," "continuous integration," "test automation pipeline." Related: playwright-automation, qa-metrics, self-healing-tests, coverage-analysis.

Design analytics-driven browser test matrices and execute cross-browser tests. Covers BrowserStack/Sauce Labs configuration, Playwright browser channels, common cross-browser CSS/JS issues, and progressive enhancement validation. Use when: "cross-browser," "browser matrix," "BrowserStack," "Safari issues," "browser compatibility," "IE/Edge." Related: visual-testing, playwright-automation, ci-cd-integration.

Build Cypress test suites with component testing, E2E testing, custom commands, cy.intercept for network control, Cypress Cloud integration, and TypeScript configuration. Covers retry-ability, command queue concepts, and data-driven testing with fixtures. Use when: "Cypress," "cy.," "component test," "Cypress Cloud," "cy.intercept." Related: ci-cd-integration, visual-testing, unit-testing.

Design and execute structured exploratory testing sessions. Covers Session-Based Test Management (SBTM), charter writing, heuristic-based exploration (HICCUPS, FEW HICCUPS), bug discovery patterns, note-taking templates, and conversion of findings to automated tests. Use when: "exploratory testing," "SBTM," "manual testing," "bug hunting," "test charter," "heuristic testing." Related: test-planning, bug-reporting, risk-based-testing.

jobs: old-suite: name: "E2E Tests (Cypress) [Legacy]" runs-on: ubuntu-latest

Set up QA dashboards and reporting with Allure Report, Grafana, and ReportPortal. Covers test execution visualization, stakeholder-facing quality reports, trend analysis panels, and CI integration for automated report generation. Use when: "test dashboard," "Allure," "test report," "quality dashboard," "Grafana testing," "ReportPortal," "test results visualization." Related: qa-metrics, ci-cd-integration, ai-bug-triage.

Define, track, and act on QA metrics. Covers test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, dashboard recommendations, and realistic targets by company stage. No other skills repo covers QA metrics comprehensively. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate," "test dashboard." Related: qa-dashboard, coverage-analysis, ci-cd-integration, qa-retrospective.

Set up your QA project context. Creates and fills .agents/qa-project-context.md with your tech stack, test frameworks, CI/CD pipeline, environments, coverage goals, risk areas, and team structure. Every other QA skill reads this file first to skip redundant questions and give context-aware recommendations. Use when: "set up QA context," "configure testing," first use of any QA skill, "initialize project."

Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Related: bug-reporting, qa-metrics, qa-dashboard, quality-postmortem.

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem meeting templates with action item tracking. Use when: "QA retro," "test review," "escaped bugs," "postmortem," "quality incident," "improvement," "defect analysis." Related: qa-metrics, test-reliability, test-strategy.

canary_to_10_percent: hold_duration: 30m conditions: - metric: error_rate_5xx comparison: less_than threshold: 0.5% window: 15m - metric: latency_p95 comparison: less_than threshold: 500ms window: 15m - metric: crash_rate comparison: equals threshold: 0 window: 15m

Decision framework for dependency isolation in tests. When to use mocks, stubs, fakes, record-replay, or ephemeral real services. Covers WireMock, MSW (Mock Service Worker), toxiproxy, and test containers. Helps choose the right isolation strategy for each testing scenario. Use when: "mock service," "stub API," "fake service," "WireMock," "MSW," "test isolation," "dependency management." Related: contract-testing, test-environments, api-testing, test-data-management.

**Sprint dates:** [start] - [end] **Features in scope:** [list with ticket IDs] **Test lead:** [name] **Last updated:** [date]

Write effective unit tests with Jest, Vitest, or pytest. Covers mocking strategies (stubs, spies, mocks, fakes), coverage configuration and meaningful thresholds, snapshot testing, mutation testing with Stryker/mutmut, test doubles taxonomy, and the Arrange-Act-Assert pattern. Use when: "unit test," "Jest," "Vitest," "pytest," "mock," "coverage," "test doubles," "mutation testing." Related: coverage-analysis, ci-cd-integration, ai-test-generation, shift-left-testing.