Playwright CI Skill for Claude

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

37k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

4468

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/zebbern/claude-code-guide --skill playwright-ci

What comes with it

147 155 bytes besides the instruction

ci-github-actions.md

ci-gitlab.md

ci-other.md

docker-and-containers.md

global-setup-teardown.md

parallel-and-sharding.md

projects-and-dependencies.md

reporting-and-artifacts.md

test-coverage.md

The instruction itself

6 sections, as written by the author

Playwright CI/CD

> Ship reliable tests in every pipeline — CI-specific patterns for speed, stability, and actionable reports.

9 guides covering CI/CD setup, parallel execution, containerized runs, reporting, and infrastructure patterns for all major CI providers.

Golden Rules

retries: 2 in CI only — surface flakiness in pipelines, not locally
traces: 'on-first-retry' — capture rich debugging artifacts without slowing every run
Shard across runners — --shard=N/M splits tests evenly; scale horizontally, not vertically
Cache browser binaries — ~/.cache/ms-playwright keyed on Playwright version
Upload artifacts on failure — traces, screenshots, and HTML reports as CI artifacts
Use the official Docker image — mcr.microsoft.com/playwright:v* has all OS deps pre-installed
Global setup for auth — run login once in globalSetup, reuse storageState across workers
Fail fast, debug later — keep CI runs short; use trace viewer and HTML reports to investigate

Guide Index

CI Providers

| Provider | Guide |

| --------------------------------- | -------------------------------------------- |

| GitHub Actions | ci-github-actions.md |

| GitLab CI | ci-gitlab.md |

| CircleCI / Azure DevOps / Jenkins | ci-other.md |

Execution & Scaling

| Topic | Guide |

| ----------------------------- | ------------------------------------------------------------ |

| Parallel execution & sharding | parallel-and-sharding.md |

| Docker & containers | docker-and-containers.md |

| Multi-project config | projects-and-dependencies.md |

Reporting & Setup

| Topic | Guide |

| --------------------- | -------------------------------------------------------- |

| Reports & artifacts | reporting-and-artifacts.md |

| Code coverage | test-coverage.md |

| Global setup/teardown | global-setup-teardown.md |

Other skills for the same job

different authors, same section of the catalogue

Azure Resource Manager Playwright Dotnet

by lingxling

×1

Azure Resource Manager SDK for Microsoft Playwright Testing in .NET.

Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.

1k tokens

Frontend Engineer

by nanocoai

Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Pairs with a deployment skill such as vercel-cli, where one is installed.

Deploy serverless browser automation as cloud functions using Browserbase. Use when the user wants to deploy browser automation to run on a schedule or cron, create a webhook endpoint for browser tasks, run automation in the cloud instead of locally, or asks about Browserbase Functions.

2k tokens

Azure Microsoft Playwright Testing Ts

by microsoft

vendor

Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.

2k tokens

Azure Playwright Workspaces

by MicrosoftDocs

Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or run/AADSTS7000112 issues, and other Playwright Workspaces related development tasks. Not for Azure App Testing (use azure-app-testing), Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure Test Plans (use azure-test-plans).

2k tokens

Yolo

by aiskillstore

| Uses Lovable MCP (preferred) or browser automation to submit deployment prompts. Runs verification tests based on configuration. Auto-deploys after git push when enabled.

112k tokens

Playwright CI

by testdino-hq

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

36k tokens

How to use it

Copy the folder

Take zebbern/playwright-ci from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.