playwright-ci
Skill1 starsChanged 35 days agoMITView on GitHub
CI and delivery skill for Playwright automation. Use when the agent needs to design, debug, or optimize Playwright execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use this skill when the main problem is pipeline execution rather than test authoring.
- Distinctive: line 23
Prefer deterministic setup over clever pipeline shortcuts.
- Distinctive: line 27
Keep CI retries informative, not silent flake camouflage.
- Distinctive: line 43
When solving CI tasks, prefer:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Playwright CI
Use this skill when the main problem is pipeline execution rather than test authoring.
CI Standards
- Prefer deterministic setup over clever pipeline shortcuts.
- Capture traces, screenshots, and reports where they help triage failures quickly.
- Scale horizontally with sharding before over-sizing single runners.
- Cache browser binaries and other stable dependencies deliberately.
- Keep CI retries informative, not silent flake camouflage.
Read by Need
| Need | Guide |
| GitHub Actions | ci-github-actions.md |
| GitLab CI | ci-gitlab.md |
| Other providers | ci-other.md |
| Sharding and scaling | parallel-and-sharding.md, projects-and-dependencies.md |
| Containers | docker-and-containers.md |
| Reports and artifacts | reporting-and-artifacts.md |
| Coverage and setup orchestration | test-coverage.md, global-setup-teardown.md |
Output Bias
When solving CI tasks, prefer:
- concrete workflow or pipeline changes,
- exact commands and cache locations,
- artifact and failure-diagnostics recommendations,
- explicit tradeoffs when the pipeline needs faster feedback versus deeper debugging.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- zebbern/claude-code-guide★ 4.7k18% same
- testdino-hq/playwright-skill★ 39318% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- playwright-analysis-requirementsSkill
- playwright-coreSkill
- playwright-migrationSkill
- playwright-orchestratorSkill
- playwright-cliSkill
- playwright-pomSkill
- playwright-skillSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.