fix-test

Diagnose and fix flaky Playwright tests with a four-phase debugging workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Cottage-Energy/cottage-tests --skill fix-test-cottage-energy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-test
Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/fix-test
Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill fix-test-cottage-energy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix a failing or flaky Playwright test.

Core Features & Use Cases

  • Structured diagnostic workflow: gather evidence → identify what changed → see the live app → fix the root cause → verify.
  • Systematic debugging across CI and local runs, including failure evidence collection, root-cause analysis, live app inspection, and verification steps.
  • Comprehensive Phase-driven approach with anti-rationalization guards and robust standards, enabling consistent, reproducible fixes.

Quick Start

Begin by gathering failure evidence from CI and local runs, then follow the four-phase root-cause process to implement and verify a fix.

Frequently Asked Questions about fix-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright e2e tests?▼

Fix flaky Playwright tests using a four-phase workflow: gather failure evidence, identify what changed, inspect the live app, and verify the root-cause fix. This ensures consistent, reproducible fixes across CI and local runs.

What is the best way to debug failing Playwright tests in CI?▼

Debug failing Playwright tests by systematically collecting failure evidence from CI and local runs, performing root-cause analysis, and enforcing structured guidance with anti-rationalization guards to verify fixes before completion.

How do I maintain page-object integrity when fixing e2e test failures?▼

Maintain page-object integrity during test fixes by following a phase-driven diagnostic workflow that enforces structured guidance and robust standards, ensuring fixtures and page objects remain intact throughout the root-cause analysis.

When do I need a structured diagnostic workflow for Playwright test debugging?▼

You need a structured diagnostic workflow when Playwright tests fail or behave flaky across environments. It guides evidence collection, live app inspection, and root-cause analysis to prevent rationalizing failures instead of verifying actual fixes.

Does this Playwright test debugging approach work for both local and CI runs?▼

Yes, this approach works for both CI and local runs. It systematically gathers failure evidence from both environments and applies a four-phase root-cause process to implement and verify fixes consistently.

Why do my Playwright e2e tests keep failing after I apply fixes?▼

Tests keep failing when fixes target symptoms rather than root causes. A structured workflow enforces live app inspection and anti-rationalization guards, verifying the actual root-cause fix before completion to prevent recurring flakiness.