fix
/fix
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".
- Author
- alirezarezvani ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author description
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".
How it works
- Input
- Steps
- Output
SKILL.md preview
--- name: "fix" description: >- 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". --- # Fix Failing or Flaky Tests Diagnose and fix a Playwright test that fails or passes intermittently using a systematic taxonomy. ## Input `$ARGUMENTS` contains: - A test file path: `e2e/login.spec.ts` - A test name: ""should redirect after login"` - A description: `"the checkout test fails in CI but passes locally"` ## Steps ### 1. Reproduce the Failure Run the test to capture the error: ```bash npx playwright test <file> --reporter=list ``` If the test passes, it's likely flaky. Run burn-in: ```bash npx playwright test <file> --repeat-each=10 --reporter=list ``` If it still passes, try with parallel workers: ```bash npx playwright test --fully-parallel --workers=4 --repeat-each=5 ``` ### 2. Capture Trace Run with full tracing: ```bash npx playwright test <file> --trace=on --retries=0 ``` Read the trace output. Use `/debug` to analyze trace files if available. ### 3. Categorize the Failure Load `flaky-taxonomy.md` from this skill directory. Every failing test falls into one of four categories: | Category | Symptom | Diagnosis | |---|---|---| | **Timing/Async** | Fails intermittently everywhere | `--repeat-each=20` reproduces locally | | **Test Isolation** | Fails in suite, passes alone | `--workers=1 --grep "test name"` passes | | **Environment** | Fails in CI, passes locally | Compare CI vs local screenshots/traces | | **Infrastructure** | Random, no pattern | Error references browser internals | ### 4. Apply Targeted Fix **Timing/Async:** - Replace `waitForTimeout()` with web-first assertions - Add `await` to missing Playwright calls - Wait for specific network responses before asserting - Use `toBeVisible()` before interacting with elements **Test Isolation:** - Remove shared mutable state between tests - Create test data per-test via API or fixtures - Use unique identifiers (timestamps, random strings) for test data - Check for database state leaks **Environment:** - Match viewport sizes between local and CI - Account for font rendering differences in screenshots - Use `docker` locally to match CI environment - Check for timezone-dependent assertions **Infrastructure:** - Increase timeout for slow CI runners - Add retries in CI config (`retries: 2`) - Check for browser OOM (reduce parallel workers) - Ensure browser dependencies are installed ### 5. Verify the Fix Run the test 10 times to confirm stability: ```bash npx playwright test <file> --repeat-each=10 --reporter=list ``` All 10 must pass. If any fail, go back to step 3. ### 6. Prevent Recurrence Suggest: - Add to CI with `retries: 2` if not already - Enable `trace: 'on-first-retry'` in config - Add the fix pattern to project's test conventions doc ## Output - Root cause category and specific issue - The fix applied (with diff) - Verification result (10/10 passes) - Prevention recommendation
Files in this package (2)
- SKILL.md 3 KB
- flaky-taxonomy.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alirezarezvani/claude-skills | 100 | MIT |
| swingerman/engineer | 100 | MIT |
| Hainrixz/claude-seo-ai | 100 | MIT |
| vanducng/skills | 100 | MIT |
| RemiPelloux/kill-my-idea | 100 | MIT |
| tony/skills | 100 | MIT |
| applelog/nondev-kit | 100 | MIT |
| A7-studio/jobmigo | 100 | MIT |
| koda-ai-studio/agent-bom | 100 | Apache-2.0 |
Identical content appears in 3 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5e1cc5456faa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fix-test
Auto-diagnose and fix failing tests — up to 3 attempts with re-runs. Triggers on: fix test, failing test, broken test, test error, why is this test failing, debug test. - 100v1-e2e-testing
Use when implementing or debugging browser end-to-end tests, especially Playwright or flaky tests. Triggers on "E2E test", "Playwright", or "flaky browser test". - 100fixing-flaky-e2e-tests
Diagnose and fix flaky Playwright e2e tests. Use when tests fail intermittently, show timeout errors, have snapshot mismatches, or exhibit browser-specific failures. - 100flaky-test-management
When the user wants to detect, triage, root-cause, quarantine, or eliminate flaky tests. Use when the user mentions "flaky tests," "intermittent failures," "test instability," "retry strategy," "test quarantine," "deflaking," "test reliability," "skip flaky test," "test that… - 100debug-e2e-test
Debug and fix failing Playwright E2E tests. Use when tests fail, when asked to fix failing tests, or when investigating test failures. Analyzes test output, screenshots, error context, and uses Playwright MCP to identify root causes. - 100axiom-analyze-test-failures
Use when the user mentions flaky tests, tests that pass locally but fail in CI, race conditions in tests, or needs to diagnose WHY a specific test fails.