Tests
End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/Cypress-skill --skill testsAssembled 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
Automation-code documentation skill for Cypress suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Cypress tests without drowning the code in redundant commentary.
SKILL.md
1.8 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)
Documenting Existing Tests
Use this skill to improve readability of existing Cypress code.
Action
- Read the target spec or support module first.
- Identify where documentation would materially help a future maintainer.
- Add concise documentation at the file, suite, test, helper, command, or page-object level as appropriate.
Commenting rules:
- Prefer high-signal docblocks over line-by-line narration.
- Explain intent, scope, business meaning, or non-obvious behavior.
- Do not restate code that is already obvious from the test title or method name.
- Avoid comment spam in straightforward tests.
After editing, summarize what was documented, why those locations mattered, and any areas that likely need refactoring rather than more comments.