Loading...
Loading...
Found 27 Skills
Compares two test runs to identify new failures, newly flaky tests, fixed tests, and duration regressions. Can be invoked with test run IDs, dashboard URLs, or branch names.
Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.
World-class QA engineering - systematic testing, automation, and the mindset that finds bugs before users doUse 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.
Show test status from last run (without re-executing)
Use this skill when deciding what to test, choosing between test types, designing a testing strategy, or balancing test coverage. Triggers on test pyramid, unit vs integration vs e2e, contract testing, test coverage strategy, TDD, BDD, testing ROI, and any task requiring testing architecture decisions.
This skill should be used when user asks about "Playwright", "responsiveness test", "test with playwright", "test login flow", "file upload test", "handle authentication in tests", or "fix flaky tests".
Analyze and optimize pytest suites to improve speed, identify flaky tests, and increase coverage. Use to maintain high-quality, fast-running test pipelines.
Write, review, or debug end-to-end tests using Playwright. Use when asked to 'write e2e tests', 'add Playwright tests', 'test this user flow', 'fix flaky tests', 'create a test suite', or 'debug this e2e failure'. Invoke with /playwright-e2e or when user mentions e2e tests, Playwright, or test automation. Do NOT use for live browser interaction via MCP tools — use playwright-mcp for that. Do NOT use for unit/integration tests — use tdd-guide agent instead.
QCSD Verification phase swarm for CI/CD pipeline quality gates using regression analysis, flaky test detection, quality gate enforcement, and deployment readiness assessment. Consumes Development outputs (SHIP/CONDITIONAL/HOLD decisions, quality metrics) and produces signals for Production monitoring.
Identify and fix flaky E2E tests by running them repeatedly and investigating failures.
Deterministic CI/CD interaction patterns. Push-and-wait discipline, failure triage, self-healing for lint/format/infra failures, structured output for pipeline consumption. Activate when interacting with CI/CD systems.
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".