playwright-pro

Solid

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.

Testing & QA 46 stars 7 forks Updated 3 days ago MIT

Install

Quality Score: 84/100

Stars 20%

56

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

50

License 10%

100

Description 5%

100

Skill Content

# 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 playwrigh...

Details

Author: adriannoes
Repository: adriannoes/awesome-agentic-ai
Created: 9 months ago
Last Updated: 3 days ago
Language: Jupyter Notebook
License: MIT

Integrates with

Playwright · Testing

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

playwright

When the user wants to design, implement, debug, stabilize, or scale Playwright tests. Use when the user mentions "Playwright," "playwright.config.ts," "page.locator," "page.getByRole," "browser context," "fixtures," "test.beforeEach," "trace viewer," "codegen," "Playwright Test," "Playwright MCP," "PWT," "WebKit testing," or "cross-browser." For Cypress-specific questions see cypress. For Selenium-specific questions see selenium. For CI sharding and parallelism see ci-test-orchestration. For screenshot diffing see visual-regression.

1 Updated 2 days ago

Testing & QA Listed

playwright-tester

Author persistent Playwright .spec.ts tests, run them natively with `npx playwright test` (zero AI tokens per run), and fix failures in a diagnose-first loop. Use whenever the user wants to test a web app, check whether a frontend works, run or re-run UI tests, verify a form or login flow, do end-to-end testing, reproduce a UI bug, smoke test a site, catch a visual regression, check for broken links, test across browsers, add regression coverage, audit every component, sweep a codebase for UI bugs, or confirm recent changes did not break anything. Also triggers on "run my e2e tests", "my playwright tests are failing", "check the app in a browser", "does this page still work after my change", "test the happy path", "write e2e tests", "set up playwright", "find UI bugs", or "test the whole app and tell me what is broken". Prefer this over driving a browser live or screenshot-based checking for anything that should be verifiable more than once.

1 Updated today

Testing & QA Listed

pw-playwright-fieldkit

Explore, debug, audit, compare, record, and test live websites with deterministic Playwright scripts and QE workflows. Use for requests to map a site, find broken pages or links, reproduce browser bugs, discover hidden or role-gated features, audit accessibility/performance, compare crawls, design or review test cases from feature specifications, record a user-demonstrated journey, execute an approved test-case document as a witnessed journey, run existing permanent automated Playwright tests with trace evidence, create test charters, find automation coverage gaps, plan test data or execution matrices, generate negative-path tests, triage flaky tests, save authenticated state, or generate verified Python/Node integration tests.

1 Updated 1 weeks ago