Migrate to Playwright

Migrates existing Cypress or Selenium test suites to Playwright, converting test files and providing guidance on best practices. It produces converted test files, a migration summary, and updated CI configuration.

✨ What it does

  • Detects the source framework (Cypress or Selenium) automatically.
  • Assesses migration scope and categorizes effort by file count.
  • Provides step-by-step conversion with mapping references for Cypress and Selenium.
  • Upgrades locators to Playwright best practices (role-based, test IDs).
  • Converts custom commands and utilities to Playwright fixtures or helpers.
  • Verifies each converted file with npx playwright test and guides cleanup.

🎯 When to use it

  • When the user mentions migrating from Cypress or Selenium to Playwright.
  • When the user asks to convert specific test files to Playwright.
  • When the user wants to switch their test framework to Playwright.
  • When the user mentions 'cypress', 'selenium', 'migrate tests', 'convert tests', 'switch to playwright', 'move from cypress', or 'replace sel

🚀 How to use

Trigger: /batch

Trigger the skill by mentioning migration from Cypress or Selenium, or by using the slash command /migrate with optional arguments like from cypress, from selenium, or a file path. If no arguments are given, it auto-detects the source framework. The skill expects an existing Cypress or Selenium test suite in the project. Example prompts:

/migrate from cypress
Convert my Selenium tests to Playwright.

📄 Output: Converted Playwright test files, a migration summary, and updated CI configuration.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering-team/playwright-pro/skills/migrate .claude/skills/migrate

Skill source: engineering-team/playwright-pro/skills/migrate/SKILL.md

⚠️ Good to know

Requires an existing Cypress or Selenium test suite; some tests may need manual intervention if they cannot be auto-converted.

❓ FAQ

What source frameworks does the skill support?

It supports migrating from Cypress and Selenium (including Python Selenium).

How does the skill handle large test suites?

For large suites (31+ files), it recommends using the /batch command for parallel conversion.

Does the skill delete old test files automatically?

No, it asks the user before deleting anything during cleanup.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.