playwright-ci — Claude Code skill: CI/CD for Playwright
A skill with ready-made CI/CD configs for Playwright: GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins and Docker. Useful once the tests exist but the pipeline keeps failing.
npx skills add testdino-hq/playwright-skill --skill playwright-ci -a claude-code
npx skills add testdino-hq/playwright-skill --skill ci -a claude-codeWhat playwright-ci does
Nine guides ship inside: CI setup for the major providers, parallel runs and sharding, containerized execution, reports and artifacts, code coverage, global setup and teardown. Each guide is its own file, like ci-github-actions.md or parallel-and-sharding.md, and the agent picks the one matching your task.
A set of rules anchors the advice. Retries belong in CI only, so flakiness shows up in the pipeline instead of on your laptop. Traces are captured on the first retry. Tests get split across runners with --shard=N/M, browser binaries are cached in ~/.cache/ms-playwright keyed on the Playwright version, and artifacts upload when a run fails.
For containers the skill points at the official image mcr.microsoft.com/playwright:v*, which already carries the OS dependencies. Auth is meant to run once in globalSetup, with storageState reused across workers. If your tests only ever run locally and there is no pipeline, these guides have nothing to attach to.
What it helps with
- wire Playwright into a GitHub Actions workflow
- split a test suite across sharded runners
- cache browser binaries between CI runs
- upload traces and an HTML report when tests fail
- move login into globalSetup and reuse storageState
Example prompts for the agent
- Set up Playwright in GitHub Actions with sharding across 4 runners
- Upload traces and the HTML report when the test job fails
- Rewrite our Playwright config so authentication runs once in globalSetup
How to install playwright-ci
1Skills CLI (Vercel)
npx skills add testdino-hq/playwright-skill --skill playwright-ci -a claude-codenpx skills add testdino-hq/playwright-skill --skill ci -a claude-code2Manually: put the files in place
~/.claude/skills/ci/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ci/
1Skills CLI (Vercel)
npx skills add testdino-hq/playwright-skill --skill ci -a codex2Manually: put the files in place
.agents/skills/ci/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add testdino-hq/playwright-skill --skill ci -a cursor2Manually: put the files in place
.cursor/skills/ci/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install testdino-hq/playwright-skill ci2Manually: put the files in place
.github/skills/ci/SKILL.md1Skills CLI (Vercel)
npx skills add testdino-hq/playwright-skill --skill ci -a gemini-cli2Platform CLI
gemini skills install https://github.com/testdino-hq/playwright-skill --path ciManually: put the files in place
.devin/skills/ci/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add testdino-hq/playwright-skill --skill ci -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about playwright-ci
How do I install playwright-ci in Claude?
Run npx skills add testdino-hq/playwright-skill --skill playwright-ci -a claude-code. The skill then lands at ~/.claude/skills/ci/SKILL.md.
What does playwright-ci do?
It hands the agent nine CI/CD guides for Playwright: configs for GitHub Actions, GitLab CI, CircleCI, Azure DevOps and Jenkins, plus parallel execution, Docker, reporting, coverage and global setup.
Do I need Docker to use this skill?
No, Docker is one guide among nine. For containerized runs the skill recommends the official image mcr.microsoft.com/playwright:v*, which has the OS dependencies pre-installed.
Source text
SKILL.md · MIT
--- name: playwright-ci description: Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown. --- # Playwright CI/CD > Ship reliable tests in every pipeline — CI-specific patterns for speed, stability, and actionable reports. **9 guides** covering CI/CD setup, parallel execution, containerized runs, reporting, and infrastructure patterns for all major CI providers. ## Golden Rules 1. **`retries: 2` in CI only** — surface flakiness in pipelines, not locally 2. **`traces: 'on-first-retry'`** — capture rich debugging artifacts without slowing every run 3. **Shard across runners** — `--shard=N/M` splits tests evenly; scale horizontally, not vertically 4. **Cache browser binaries** — `~/.cache/ms-playwright` keyed on Playwright version 5. **Upload artifacts on failure** — traces, screenshots, and HTML reports as CI artifacts 6. **Use the official Docker image** — `mcr.microsoft.com/playwright:v*` has all OS deps pre-installed 7. **Global setup for auth** — run login once in `globalSetup`, reuse `storageState` across workers 8. **Fail fast, debug later** — keep CI runs short; use trace viewer and HTML reports to investigate ## Guide Index ### CI Providers | Provider | Guide | |---|---| | GitHub Actions | [ci-github-actions.md](ci-github-actions.md) | | GitLab CI | [ci-gitlab.md](ci-gitlab.md) | | CircleCI / Azure DevOps / Jenkins | [ci-other.md](ci-other.md) | ### Execution & Scaling | Topic | Guide | |---|---| | Parallel execution & sharding | [parallel-and-sharding.md](parallel-and-sharding.md) | | Docker & containers | [docker-and-containers.md](docker-and-containers.md) | | Multi-project config | [projects-and-dependencies.md](projects-and-dependencies.md) | ### Reporting & Setup | Topic | Guide | |---|---| | Reports & artifacts | [reporting-and-artifacts.md](reporting-and-artifacts.md) | | Code coverage | [test-coverage.md](test-coverage.md) | | Global setup/teardown | [global-setup-teardown.md](global-setup-teardown.md) |
© testdino-hq · MIT · testdino-hq/playwright-skill
