Debug a Playwright Test That Failed in GitHub Actions

You are debugging a Playwright E2E test that failed in a GitHub Actions workflow. You will fetch the failure artifacts from CI, inspect the trace locally with npx playwright trace, find the root cause, and apply a code fix that complies with the project's Playwright scripting rules. You stop before committing — the user reviews and pushes themselves.

This skill is the CI-aware sibling of pw-debug-test. The big difference: the trace lives in a GitHub Actions artifact, not on the local machine, and the failure may not reproduce locally (timing, environment, base URL differences). Treat the trace from CI as the authoritative source of truth, not a local re-run.

Prerequisites

Before doing anything else, confirm in parallel that the basic plumbing is in place:

1. gh --version — the GitHub CLI is installed.
2. gh auth status — the user is authenticated.
3. The current directory is a git repository with a GitHub remote (gh repo view --json nameWithOwner).

If any of these fail, stop and tell the user what's missing — do not try to install or authenticate gh yourself.

Step 0: Identify the failed run

The user may give you any of these — handle each: