cypress-ci
Skill0 starsChanged 35 days agoMITView on GitHub
CI and delivery skill for Cypress automation. Use when the agent needs to design, debug, or optimize Cypress 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
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 retries informative, not silent flake camouflage.
- Distinctive: line 28
Prefer explicit browser and environment selection in CI.
- Distinctive: line 58
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
Cypress CI/CD
Use this skill when the main problem is pipeline execution rather than test authoring.
Golden Rules
- Prefer deterministic setup over clever pipeline shortcuts.
- Capture screenshots, videos, reports, and other artifacts where they materially reduce triage time.
- Scale horizontally with sharding only after test data and isolation are under control.
- Cache stable dependencies deliberately, including the Cypress binary and package-manager state where appropriate.
- Keep retries informative, not silent flake camouflage.
- Prefer explicit browser and environment selection in CI.
Official References
- Cypress best practices: https://docs.cypress.io/guides/references/best-practices
CI Compatibility Matrix
| Layer | Supported range | CI guidance |
| Cypress | >=13.0.0 | Keep runner images aligned with your Cypress major. |
| Node.js (by Cypress major) | Cypress 13-14: >=18; Cypress 15+: 20.x, 22.x, >=24.x | Pin Node explicitly in pipeline config to avoid drift. |
| OS runners | Linux (Ubuntu 22+), Windows 10+/Server 2019+, macOS 13+ | Match Cypress system requirements for browser dependencies. |
| Package managers | npm >=10.1, pnpm >=8, Yarn modern >=4, Yarn classic >=1.22.22 | Install failures are often package-manager floor issues. |
| Browsers | Chrome, Firefox, Edge, Electron | Use explicit browser flags in CI for deterministic behavior. |
Guides
| 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, cache locations, and artifact paths,
- explicit diagnostics and validation steps,
- clear tradeoffs when the pipeline needs faster feedback versus deeper debugging.
Other versions1 project uses a version of this.
Word for word · 1
- jovd83/Cypress-skill★ 0100% same
Edited · 0
None found.
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.
- cypress-analysis-requirementsSkill
- cypress-coreSkill
- cypress-cliSkill
- cypress-migrationSkill
- cypress-orchestratorSkill
- cypress-pomSkill
- cypress-skillSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.