Ci
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill ciAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
CI and delivery skill for Playwright automation. Use when Codex 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.
SKILL.md
2.1 KB, as published. Nobody here has run it
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.