playwright-pro

Generate, review, and repair Playwright end-to-end tests with CI and cross-browser integrations.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/lagarcess/argus --skill playwright-pro-lagarcess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-pro
Source: https://github.com/lagarcess/argus/tree/main/.agent/skills/playwright-pro
Command: npx skills add https://github.com/lagarcess/argus --skill playwright-pro-lagarcess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright Pro eliminates slow, flaky, and inconsistent end-to-end test workflows by automating test generation, enforcing robust locator/assertion patterns, and providing production-ready CI and reporting integrations so teams spend less time debugging tests and more time shipping features.

Core Features & Use Cases

  • Scaffolds Playwright configuration, baseURL, CI pipelines, and recommended retries/traces for production use.
  • Generates parametrizable TypeScript/JavaScript tests from user stories, URLs, or components using 55 templates (auth, CRUD, checkout, accessibility, API, etc.).
  • Reviews and fixes flaky or failing tests by detecting locator anti-patterns, replacing waitForTimeout with web-first assertions, and applying auto-fixes.
  • Migrates suites from Cypress or Selenium to Playwright and analyzes coverage parity before decommissioning legacy tests.
  • Integrates with TestRail and BrowserStack for test case sync and cross-browser execution; produces smart reports and trace-enabled diagnostics.
  • Provides specialized agents (test-architect, test-debugger, migration-planner), golden rules, locator priority guidelines, and extensive references for test quality.

Quick Start

Run the Playwright Pro init workflow to scaffold Playwright configuration, CI pipelines, and a first smoke test for your project.

Frequently Asked Questions about playwright-pro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright tests using web-first assertions?

Migrate Cypress or Selenium test suites to Playwright by analyzing coverage parity before decommissioning legacy tests. The migration-planner agent converts existing browser automation scripts while ensuring functional equivalence across the migrated e2e-testing workflows.

Can I generate Playwright tests from user stories or URLs?

Generate parametrizable TypeScript and JavaScript Playwright tests from user stories, URLs, or components using 55 templates covering auth, CRUD, checkout, accessibility, and API scenarios. The test-architect agent scaffolds these e2e-testing scripts with production-ready locator strategies.

Does Playwright work with BrowserStack and TestRail for cross-browser execution?

Playwright integrates with TestRail for test case synchronization and BrowserStack for cross-browser execution. These e2e-testing integrations produce smart reports and trace-enabled diagnostics that map automation results back to test management platforms.

How do I scaffold Playwright configuration and CI pipelines for production?

Scaffold production-grade Playwright configuration including baseURL, CI pipelines, recommended retries, and traces by running the init workflow. This test-automation setup generates a robust config file and an initial smoke test to establish reliable e2e-testing foundations.

What is the best way to measure test coverage when migrating from Cypress to Playwright?

Measure test coverage during Cypress to Playwright migration by analyzing coverage parity before decommissioning legacy tests. The migration-planner evaluates existing e2e-testing suites to ensure functional equivalence and prevent gaps in test-automation coverage.