Playwright Pro 2.1.1

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test mi...

Security Scan

The skill's files, instructions, hooks, and optional integrations are consistent with a Playwright testing toolkit — nothing requests unexplained credentials or performs unrelated actions, though it will read and run local test-related tooling when used.

Purpose & Capability

Name/description (Playwright test generation, review, fix, migration, BrowserStack/TestRail integrations) match the included assets: templates, agents (migration-planner, test-architect, test-debugger), hooks to detect/validate Playwright tests, and two MCP integration clients for BrowserStack and TestRail. There are no unrelated binaries or environment requirements declared.

Instruction Scope

SKILL.md and CLAUDE.md limit actions to test generation, review, debugging, migration and optional external integrations. The agents are allowed to read the repo (Read/Grep/Glob/LS) and the test-debugger may run Bash commands (it explicitly runs npx playwright test). Hooks run two shell scripts: detect-playwright.sh (on session start) and validate-test.sh (on PostToolUse Write/Edit). These scripts inspect repository files and test files for anti-patterns — expected for the skill but worth noting because they operate on local files and may run automatically after writes.

Install Mechanism

There is no automated install spec (instruction-only), which minimizes automatic disk writes. However, the skill bundle contains runnable code (TypeScript MCP servers and shell hooks). Running those MCP servers or hooks requires Node/tsx/python3/bash on the host and would be a manual action by the user or the platform's plugin runtime. No remote download URLs or extract steps are present.

Credentials

The manifest declares no required environment variables. The SKILL.md documents optional env vars for TestRail (TESTRAIL_URL/USER/API_KEY) and BrowserStack (BROWSERSTACK_USERNAME/ACCESS_KEY) that are appropriate for those integrations. No unrelated credentials are requested. The MCP server code checks for those env vars and exits if they are absent, which matches the 'optional integration' behavior.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent platform-wide privileges. Hooks are present and configured to run on SessionStart and after write/edit operations (PostToolUse), which is consistent with a developer tooling plugin that validates tests. The skill does not attempt to modify other skills' config or request elevated system-wide settings.

Assessment

This skill appears coherent with its stated purpose. Things to consider before installing or enabling it: 1) Hooks will run shell scripts on session start and after file writes — they inspect your repository and validate test files; review hooks/validate-test.sh and hooks/detect-playwright.sh if you want to confirm exact behavior. 2) The BrowserStack and TestRail integrations are optional but require credentials (env vars) to operate; only provide those credentials if you intend to use those integrations. 3) The package includes TypeScript 'MCP' servers (BrowserStack/TestRail) that will perform network calls when you run them locally — review their code and only run them in trusted environments. 4) The test-debugger agent runs Playwright commands (npx playwright test) during diagnosis; expect it to execute local tests and create traces. If any of that is undesirable, avoid starting the MCP servers or enable only the portions you trust.

Playwright Pro

Production-grade Playwright testing toolkit for AI coding agents.

Available Commands

When installed as a Claude Code plugin, these are available as /pw: commands:

Command	What it does
/pw:init	Set up Playwright — detects framework, generates config, CI, first test
/pw:generate <spec>	Generate tests from user story, URL, or component
/pw:review	Review tests for anti-patterns and coverage gaps
/pw:fix <test>	Diagnose and fix failing or flaky tests
/pw:migrate	Migrate from Cypress or Selenium to Playwright
/pw:coverage	Analyze what's tested vs. what's missing
/pw:testrail	Sync with TestRail — read cases, push results
/pw:browserstack	Run on BrowserStack, pull cross-browser reports
/pw:report	Generate test report in your preferred format

Quick Start Workflow

The recommended sequence for most projects:

1. /pw:init          → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate      → generates tests from your spec or URL
3. /pw:review        → validates quality and flags anti-patterns      ← always run after generate
4. /pw:fix <test>    → diagnoses and repairs any failing/flaky tests  ← run when CI turns red

Validation checkpoints:

• After /pw:generate — always run /pw:review before committing; it catches locator anti-patterns and missing assertions automatically.
• After /pw:fix — re-run the full suite locally (npx playwright test) to confirm the fix doesn't introduce regressions.
• After /pw:migrate — run /pw:coverage to confirm parity with the old suite before decommissioning Cypress/Selenium tests.

Example: Generate → Review → Fix

# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"

# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.

# 2. Review the generated tests
/pw:review tests/auth/login.spec.ts

# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.

# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed

# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()

Golden Rules

1. getByRole() over CSS/XPath — resilient to markup changes
2. Never page.waitForTimeout() — use web-first assertions
3. expect(locator) auto-retries; expect(await locator.textContent()) does not
4. Isolate every test — no shared state between tests
5. baseURL in config — zero hardcoded URLs
6. Retries: 2 in CI, 0 locally
7. Traces: 'on-first-retry' — rich debugging without slowdown
8. Fixtures over globals — test.extend() for shared state
9. One behavior per test — multiple related assertions are fine
10. Mock external services only — never mock your own app

Locator Priority

1. getByRole()        — buttons, links, headings, form elements
2. getByLabel()       — form fields with labels
3. getByText()        — non-interactive text
4. getByPlaceholder() — inputs with placeholder
5. getByTestId()      — when no semantic option exists
6. page.locator()     — CSS/XPath as last resort

What's Included

• 9 skills with detailed step-by-step instructions
• 3 specialized agents: test-architect, test-debugger, migration-planner
• 55 test templates: auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility
• 2 MCP servers (TypeScript): TestRail and BrowserStack integrations
• Smart hooks: auto-validate test quality, auto-detect Playwright projects
• 6 reference docs: golden rules, locators, assertions, fixtures, pitfalls, flaky tests
• Migration guides: Cypress and Selenium mapping tables

Integration Setup

TestRail (Optional)

export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="[e-mail]"
export TESTRAIL_API_KEY="your-api-key"

BrowserStack (Optional)

export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"

Quick Reference

See reference/ directory for:

• golden-rules.md — The 10 non-negotiable rules
• locators.md — Complete locator priority with cheat sheet
• assertions.md — Web-first assertions reference
• fixtures.md — Custom fixtures and storageState patterns
• common-pitfalls.md — Top 10 mistakes and fixes
• flaky-tests.md — Diagnosis commands and quick fixes

See templates/README.md for the full template index.