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.