Generation
End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/Cypress-skill --skill generationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Coverage-planning skill for Cypress work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Cypress coverage plan with scenarios, execution types, priorities, and traceability.
SKILL.md
2.6 KB, as published. Nobody here has run it
Telemetry & Logging
[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason>(or./log-dispatch.shon Linux)
Functional Coverage Plan Generation
Use this skill after the requirements are clear enough to plan against.
1. Prerequisite
- Start from confirmed requirements or a clearly labeled analysis baseline.
- If major assumptions remain, keep them visible in the plan instead of burying them.
2. Generate the Scenarios
- Aim for meaningful functional completeness, not mechanical scenario inflation.
- Cover the paths that change confidence: core success paths, important variations, failure handling, boundary conditions, permissions, and role differences when relevant.
- Avoid duplicate scenarios that test the same risk with different wording.
- Choose the lowest-cost execution type that still validates the behavior well.
Recommended scenario classes:
- Happy paths
- Important variations
- Negative and error handling
- Boundary and resilience behavior
3. Formatting the Plan
Produce a coverage plan table like this:
| Priority | Requirement ID | Scenario | Coverage Type | Execution Type | Risk Covered | Notes |
|---|
Use Execution Type values such as UI, API, or Component.
Use Coverage Type values such as happy-path, variation, negative, edge, or resilience when helpful.
4. Next Step
Use dispatcher intent review_cypress_coverage_plan when explicit review or sign-off is needed before implementation or documentation.
If dispatcher routing is unavailable, use cypress-coverage-plan-review.