Migration
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill migrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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 Playwright. Use when Codex needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
SKILL.md
1.5 KB, as published. Nobody here has run it
Playwright Migration
Use this skill when the user is moving from another browser automation stack to Playwright.
Migration Workflow
- Inventory the existing suite structure, runner assumptions, and shared helpers.
- Map framework concepts to the Playwright equivalents.
- Choose an incremental migration path that preserves confidence.
- Revisit architecture decisions such as fixtures, waiting, locators, and CI once the syntax translation is done.
Guides
| Source framework | Guide |
|---|---|
| Cypress | from-cypress.md |
| Selenium / WebDriver | from-selenium.md |
Output Bias
Prefer migration plans, translated examples, and architecture notes over abstract comparisons.