Agent skill

Playwright Regression Testing

by fugazi in fugazi/test-automation-skills-agents

Govern Playwright TypeScript regression suites across many tests.

MITAuto-check passedTesting & QA

Install Playwright Regression Testing

skills CLI
$ npx skills add fugazi/test-automation-skills-agents --skill playwright-regression-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fugazi/test-automation-skills-agents playwright-regression-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fugazi/test-automation-skills-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/playwright-regression-testing .claude/skills/playwright-regression-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
playwright-regression-testing
GitHub stars
247
Token cost
~1.4k tokens
SKILL.md length
452 words
Files
8 (incl. references)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Govern Playwright TypeScript regression suites across many tests.

  • Optimize suites with risk/change analysis
  • SKILL.md covers When to Use This Skill, Prerequisites, Quick Reference and Red Flags, plus 2 more sections
  • Calls npx
  • Flaky-test management

What it does

Playwright Regression Testing is an agent skill from fugazi/test-automation-skills-agents. Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/ci-cd-integration.md`, `references/flaky-management.md` and `references/regression-best-practices.md`).

It sits in Testing & QA, covering QA and bug reports, Browser testing and Failing and flaky tests. It works with Playwright, TypeScript and Git. The repository describes itself as: A practical library of agents, instructions, and skills designed specifically for QA Automation Engineers, focusing on production-oriented solutions. The licence is MIT.

When your agent uses it

  • Optimize suites with risk/change analysis
  • Flaky-test management
  • Suite-health metrics
  • Not for authoring one UI spec

Example prompts

  • “/playwright-regression-testing”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 65a72d5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Playwright Regression Testing loads about 1.4k tokens when it runs, and up to ~8.8k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 452 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fugazi/test-automation-skills-agents at commit 65a72d5, republished under its MIT licence (© fugazi). 452 words, ~1,356 tokens.

Download SKILL.mdSave it as .claude/skills/playwright-regression-testing/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
playwright-regression-testing
description
Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.
license
Complete terms in LICENSE.txt

Playwright Regression Testing (TypeScript)

Strategy and best practices for automated regression testing of web applications using Playwright with TypeScript.

Activation: This skill is triggered when working with regression test strategy, test suite selection, test prioritization, CI/CD pipeline testing, flaky test management, test sharding, or optimizing test execution for web applications using Playwright.

When to Use This Skill

  • Plan regression suites with risk-based and change-based test selection
  • Organize tests into tiers (smoke, sanity, selective, full regression)
  • Optimize execution with parallelization, sharding, and time-budget strategies
  • Integrate with CI/CD using GitHub Actions pipelines
  • Manage flaky tests with quarantine, retry policies, and root cause tracking
  • Monitor suite health with execution time, flake rate, and detection metrics
  • Select tests after changes using git diff analysis and impact mapping
Do NOT Use For
  • Authoring a single UI spec or page-object model (use playwright-e2e-testing).
  • Driving a live browser interactively for debugging (use playwright-cli).
  • Selenium/Java regression suites (use webapp-selenium-testing).
  • API contract testing in isolation (use api-testing).

Prerequisites

RequirementDetails
Node.jsv18+ recommended
Playwright@playwright/test package
TypeScripttypescript configured in project
BrowsersInstalled via npx playwright install
GitRequired for change-based test selection
GitHub ActionsRecommended CI/CD platform

Quick Reference

Tiers: Smoke (<2min, every commit) → Sanity (<10min, every PR) → Selective (<30min, on merge) → Full (<60min, nightly/pre-release).

Key tags: @smoke, @sanity, @regression, @e2e, @api, @destructive — exactly one per test, never on describe() blocks. Domain-specific extensions (e.g., @a11y in accessibility skills) are allowed alongside, but only one execution tag per test.

CLI: npx playwright test --grep @smoke | --grep @regression | --grep-invert @destructive | --shard=1/4 | --last-failed

For full tier model, regression types table, and tag taxonomy, see references/regression-catalogs.md.


Show full SKILL.md (188 more words)Show less

Red Flags

  • Treating flaky tests as "fixed" by adding retries or waitForTimeout — quarantine and root-cause instead.
  • Running the full suite on every commit — use tiered selection (smoke on commit, full nightly).
  • Quarantining tests silently with no tracking ticket — quarantine must be temporary and owned.
  • No change-based selection — running everything regardless of what changed wastes CI budget.
  • Ignoring suite-health metrics (rising duration, climbing flake rate) until they block releases.

References

DocumentContent
Regression StrategyTier model (smoke→full), regression types, triggers, directory layout, test tagging and tag taxonomy
Regression SelectionTest selection (change-based, risk-based, historical, time-budget) and test naming conventions
Regression Best PracticesLocator priority, web-first assertions, test independence, test.step() reporting, complete worked example test
CI/CD IntegrationGitHub Actions tiered pipeline, sharding, merge reports, Playwright config, performance optimization, CLI reference
Flaky ManagementRetry policies, quarantine strategies, detection checklist, suite health metrics, troubleshooting

Verification

  • Smoke test subset identified — Tagged @smoke tests run in under 2 minutes
  • No test duplication — Each scenario tested exactly once at the appropriate level
  • Test isolation verified — Running tests in random order produces same results as sequential
  • Flaky test baseline established — All tests pass 5/5 consecutive runs

© fugazi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills/playwright-regression-testing of fugazi/test-automation-skills-agents.

  • SKILL.md
  • LICENSE.txt
  • references/ci-cd-integration.md
  • references/flaky-management.md
  • references/regression-best-practices.md
  • references/regression-catalogs.md
  • references/regression-selection.md
  • references/regression-strategy.md

Open the folder on GitHubat commit 65a72d5

Compare with similar skills

Playwright Regression Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Playwright Regression Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Playwright Regression Testing this skillfugazi/test-automation-skills-agents247—~1.4kAutomated safety check: PassMIT
Playwright Automationpetrkindlmann/qa-skills165—~5.5kAutomated safety check: PassMIT
Debug Playwright Prowquay/quay2.8k—~2.2kAutomated safety check: PassApache-2.0
Debug Playwrightquay/quay2.8k—~1.2kAutomated safety check: PassApache-2.0
Claude Code QAPramodDutta/qaskills232—~2.3kAutomated safety check: PassMIT
Test CommanderEliasOulkadi/shokunin114—~3kAutomated safety check: NotesMIT

Similar skills

  • Playwright Automation

    petrkindlmann/qa-skills

    Write production-grade Playwright tests in TypeScript: Page Object Model, fixtures, auto-waiting, user-facing locators, parallel execution, CI integration, sharding, and 2025-2026 feature awareness.

    165 GitHub stars~5.5k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…

    2.8k GitHub stars~2.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Debug Playwright E2E test failures from GitHub Actions CI runs.

    2.8k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Claude Code QA

    PramodDutta/qaskills

    The complete QA skill for Claude Code — turn Claude into an expert QA engineer that picks the right test type, writes reliable Playwright, Cypress, and pytest tests, eliminates flaky tests, enforces…

    232 GitHub stars~2.3k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • Test Commander

    EliasOulkadi/shokunin

    Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).

    114 GitHub stars~3k tokensUpdated 3 days ago
    Testing & QAAuto-check: notes
  • E2E Testing

    aAAaqwq/AGI-Super-Team

    Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

    105 GitHub starsUsed in 6 repos~2k tokens
    Testing & QAAuto-check passed

More from fugazi/test-automation-skills-agents

All 10 skills in this repo
  • Accessibility Selenium Testing

    fugazi/test-automation-skills-agents

    Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine.

    247 GitHub stars~2.5k tokensUpdated 5 days ago
    Auto-check passed
  • API Testing

    fugazi/test-automation-skills-agents

    Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).

    247 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check passed
  • QA Manual Istqb

    fugazi/test-automation-skills-agents

    Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters.

    247 GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check passed
  • Webapp Selenium Testing

    fugazi/test-automation-skills-agents

    Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5.

    247 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed
  • A11y Playwright Testing

    fugazi/test-automation-skills-agents

    Accessibility testing for web applications using Playwright (@playwright/test), TypeScript, and axe-core.

    247 GitHub stars~3.2k tokensUpdated 5 days ago
    Auto-check passed
  • Grill Me QA

    fugazi/test-automation-skills-agents

    A guided interview to challenge and validate QA automation plans, test strategies, and framework designs before implementation.

    247 GitHub stars~3.9k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Playwright Regression Testing

What does Playwright Regression Testing do?

Govern Playwright TypeScript regression suites across many tests. Playwright Regression Testing is an agent skill from fugazi/test-automation-skills-agents. Govern Playwright TypeScript regression suites across many tests.

When should I use Playwright Regression Testing?

Playwright Regression Testing fits situations like: optimize suites with risk/change analysis; flaky-test management; suite-health metrics; not for authoring one UI spec.

How do I install Playwright Regression Testing in Claude Code?

Run `npx skills add fugazi/test-automation-skills-agents --skill playwright-regression-testing -a claude-code`. Or copy the skill folder (skills/playwright-regression-testing in fugazi/test-automation-skills-agents) into .claude/skills/playwright-regression-testing in your project. Claude Code loads it when a task matches its description.

How do I install Playwright Regression Testing in Codex?

Run `npx skills add fugazi/test-automation-skills-agents --skill playwright-regression-testing -a codex`. Or copy the skill folder (skills/playwright-regression-testing in fugazi/test-automation-skills-agents) into .agents/skills/playwright-regression-testing in your project. Codex loads it when a task matches its description.

Can I use Playwright Regression Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fugazi/test-automation-skills-agents --skill playwright-regression-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/playwright-regression-testing, .gemini/skills/playwright-regression-testing, .github/skills/playwright-regression-testing and .opencode/skills/playwright-regression-testing in your project.

What does Playwright Regression Testing need to run?

Going by SKILL.md and its folder, Playwright Regression Testing needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Playwright Regression Testing access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Playwright Regression Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Playwright Regression Testing use?

Playwright Regression Testing is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Playwright Regression Testing use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.5k tokens, read only when the agent opens those files.

What are the alternatives to Playwright Regression Testing?

Skills that share tags, products or a category with Playwright Regression Testing: Playwright Automation (petrkindlmann/qa-skills, 165 stars), Debug Playwright Prow (quay/quay, 2.8k stars), Debug Playwright (quay/quay, 2.8k stars) and Claude Code QA (PramodDutta/qaskills, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Playwright Regression Testing?

fugazi (a GitHub user) maintains it in fugazi/test-automation-skills-agents, which has 247 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 3, 2026.

Source: fugazi/test-automation-skills-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.