Playwright QA CLI

Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea

58 stars 18 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add EricTechPro/startup-claude-skills --skill playwright-qa-cli
Manual install
git clone --depth 1 https://github.com/EricTechPro/startup-claude-skills.git /tmp/startup-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-claude-skills/skills/playwright-qa-cli ~/.claude/skills/playwright-qa-cli

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Playwright QA (CLI Variant)

Automated headless-browser QA using `playwright-cli` bash commands. Provisions a test user, logs in, navigates to target pages, screenshots each step, generates REPORT.md, cleans up.

## CRITICAL: No MCP Tools

Do NOT use any `mcp__plugin_playwright_playwright__*` tools. Use ONLY `playwright-cli` bash commands via the Bash tool. If `playwright-cli` is not found, STOP and ask user to install — do NOT fall back to MCP tools.

## PATH Setup — REQUIRED

**Prefix EVERY `playwright-cli` bash command** with:
```bash
export PATH="$HOME/.npm-global/bin:$PATH" && playwright-cli ...
```

## Parameters

| Parameter | Default | Example | Description |
|-----------|---------|---------|-------------|
| `base` | `prod` | `local` | `prod` = CONFIG.md `PROD_URL`, `local` = `http://localhost:3000` |
| `mode` | `check` | `verify` | `verify` = reproduce bug, `check` = confirm fix |
| `url` | auto-detect | `/dashboard/receipts` | Page to test |
| `change_description` | from git diff | `"Fixed button overflow"` | What to verify |
| `ticket_id` | none | `PROJ-123` | Issue tracker ticket (folder naming) |
| `skip_cleanup` | `false` | `true` | Keep test user alive |

## Configuration

All project-specific settings are defined in `CONFIG.md` at the root of this skill directory. Before first use, copy `CONFIG.example.md` to `CONFIG.md` and fill in your values.

| Setting | Source |
|---------|--------|
| **Test Email** | `CONFIG.md` → `TEST_USER_EMAIL` |
Read the full skill on GitHub

Details

Skill name
playwright-qa-cli
Path
skills/playwright-qa-cli/SKILL.md
License
MIT
Repo updated
5 June 2026

FAQ

What does the Playwright QA CLI skill do?

Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea

How do I install the Playwright QA CLI skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add EricTechPro/startup-claude-skills --skill playwright-qa-cli. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Playwright QA CLI popular?

It lives in EricTechPro/startup-claude-skills, which has 58 GitHub stars and 18 forks.

Related skills

Develop Team

58

EricTechPro/startup-claude-skills

This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.

Software Development18

Fix Sentry

58

EricTechPro/startup-claude-skills

Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.

DevOps & Cloud18

Fix Ticket

58

EricTechPro/startup-claude-skills

Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.

Testing & QA18

Stress Test

45

gbasin/stress-test-skill

Adversarially stress-test a technical plan by verifying claims against real docs, running POC code, and updating the plan before you build.

Testing & QA

Drupal Testing

84

grasmash/drupal-claude-skills

Test-driven development for Drupal with PHPUnit and Drupal Test Traits (DTT). Use when writing or fixing tests, deciding what is worth a test, reproducing a bug before fixing it, choosing a bootstrap level (Unit vs Kernel vs ExistingSite/functional), testing permission gates, adding Playwright visual verification, or debugging tests that silently run zero assertions. Covers the bug-fix RED-first discipline, the worth-a-test rubric, bootstrap cost tradeoffs, negative tests, the anonymous-403 permission trap, DTT gotchas, and the PHPUnit-version pin that makes Drupal tests pass vacuously.

Testing & QA

Owasp AI Testing

74

mastepanoski/claude-skills

AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.