Migration

End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.

Install

npx -y skills add jovd83/Cypress-skill --skill migration

Assembled 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

Migration skill for moving existing UI automation to Cypress. Use when Codex needs to translate Playwright or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.

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.sh on Linux)

Cypress Migration Guides

Use this skill when the user is moving from another browser automation stack to Cypress.

Migration Workflow

Inventory the existing suite structure, runner assumptions, and shared helpers.
Map framework concepts to Cypress equivalents.
Choose an incremental migration path that preserves confidence.
Revisit architecture decisions such as waiting, selectors, network control, fixtures, and CI once the syntax translation is done.

Official References

Cypress best practices: https://docs.cypress.io/guides/references/best-practices

Guide Index

Migrating from	Guide
Playwright	from-playwright.md
Selenium / WebDriver	from-selenium.md

Output Bias

Prefer migration plans, translated examples, and architecture notes over abstract comparisons.