playwright

Automate Playwright E2E tests with root-cause diagnosis and retry workflows.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill playwright-leessju
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/leessju/claude-skills/tree/main/playwright
Command: npx skills add https://github.com/leessju/claude-skills --skill playwright-leessju

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright E2E testing with a debug-root + ultraqa pattern to automatically diagnose and fix issues in the current project, stabilizing QA cycles.

Core Features & Use Cases

  • End-to-end browser validation using Playwright CLI with deterministic execution.
  • Automatic root-cause diagnosis and iterative fixes via the ULTRAQA loop.
  • Multi-phase workflow including information gathering, script generation, execution, and reporting.

Quick Start

Describe the test scenario you want automated, and the system will generate and execute a Playwright E2E test with an automatic root-cause loop.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate Playwright E2E tests and automatically diagnose failures?

You can automate Playwright E2E tests by describing your test scenario, which generates and executes a dynamic test script with an automatic ULTRAQA-style retry loop for root-cause diagnosis and iterative fixes.

What is the ULTRAQA workflow for stabilizing browser test deployments?

The ULTRAQA workflow is a multi-phase process for stabilizing deployments that gathers information, generates dynamic test scripts, executes browser validation, and provides verbose reporting with automatic root-cause diagnosis and iterative fixes.

Can I generate dynamic Playwright test scripts from a text description?

Yes, you can generate dynamic Playwright test scripts from ARGUMENTS. You describe the test scenario you want automated, and the system dynamically generates the corresponding E2E test script for browser execution.

How do I get verbose reporting and screenshots from cross-viewport browser testing?

Cross-viewport browser testing provides verbose reporting and screenshots by executing deterministic Playwright CLI commands across multiple browsers, capturing visual evidence and detailed logs during the automatic root-cause diagnosis loop.

Do I need any specific testing dependencies installed to use this E2E debugging loop?

No specific testing dependencies are required to use this E2E debugging loop. The workflow handles browser-based validation using the Playwright CLI internally, requiring only your web project to apply the repetitive test validation and debugging loops.