Loading...
Loading...
Found 37 Skills
Debugging méthodique en 4 phases (reproduce → isolate → fix → verify). Use when investigating a bug, regression, flaky test, or unexpected behavior.
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.
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
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)
Identify and fix common testing mistakes across unit, integration, and E2E test suites. Use when tests are flaky, brittle, over-mocked, order-dependent, slow, poorly named, or providing false confidence. Use for "test smell", "fragile test", "flaky test", "over-mocking", "test anti-pattern", or "skipped tests". Do NOT use for writing new tests from scratch (use test-driven-development), refactoring architecture (use systematic-refactoring), or performance profiling without a specific test quality symptom.
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.
Compares a single test case's behavior across two branches, analyzing pass/fail status, duration, flakiness, and failure details. Useful for investigating test regressions introduced by a feature branch.
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.
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.
Review Argos visual regression builds as one input to a pull request review. Use when a PR has an Argos build link, an Argos status check, or a bot comment pointing to an Argos build, and you need to decide whether the visual diffs match the developer's intent before approving.
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.