/ci
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.
$ npx -y skills add zebbern/claude-code-guide --skill ci --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ci
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
ci.SKILL.mdname: playwright-ci
description: 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.
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
1. **`retries: 2` in CI only** — surface flakiness in pipelines, not locally 2. **`traces: 'on-first-retry'`** — capture rich debugging artifacts without slowing every run 3. **Shard across runners** — `--shard=N/M` splits tests evenly; scale horizontally, not vertically 4. **Cache browser binaries** — `~/.cache/ms-playwright` keyed on Playwright version 5. **Upload artifacts on failure** — traces, screenshots, and HTML reports as CI artifacts 6. **Use the official Docker image** — `mcr.microsoft.com/playwright:v*` has all OS deps pre-installed 7. **Global setup for auth** — run login once in `globalSetup`, reuse `storageState` across workers 8. **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](ci-github-actions.md) | | GitLab CI | [ci-gitlab.md](ci-gitlab.md) | | CircleCI / Azure DevOps / Jenkins | [ci-other.md](ci-other.md) |
Execution & Scaling
| Topic | Guide | | ----------------------------- | ------------------------------------------------------------ | | Parallel execution & sharding | [parallel-and-sharding.md](parallel-and-sharding.md) | | Docker & containers | [docker-and-containers.md](docker-and-containers.md) | | Multi-project config | [projects-and-dependencies.md](projects-and-dependencies.md) |
Reporting & Setup
| Topic | Guide | | --------------------- | -------------------------------------------------------- | | Reports & artifacts | [reporting-and-artifacts.md](reporting-and-artifacts.md) | | Code coverage | [test-coverage.md](test-coverage.md) | | Global setup/teardown | [global-setup-teardown.md](global-setup-teardown.md) |
Read more
name: playwright-ci description: 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.
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
1. **`retries: 2` in CI only** — surface flakiness in pipelines, not locally 2. **`traces: 'on-first-retry'`** — capture rich debugging artifacts without slowing every run 3. **Shard across runners** — `--shard=N/M` splits tests evenly; scale horizontally, not vertically 4. **Cache browser binaries** — `~/.cache/ms-playwright` keyed on Playwright version 5. **Upload artifacts on failure** — traces, screenshots, and HTML reports as CI artifacts 6. **Use the official Docker image** — `mcr.microsoft.com/playwright:v*` has all OS deps pre-installed 7. **Global setup for auth** — run login once in `globalSetup`, reuse `storageState` across workers 8. **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](ci-github-actions.md) | | GitLab CI | [ci-gitlab.md](ci-gitlab.md) | | CircleCI / Azure DevOps / Jenkins | [ci-other.md](ci-other.md) |
Execution & Scaling
| Topic | Guide | | ----------------------------- | ------------------------------------------------------------ | | Parallel execution & sharding | [parallel-and-sharding.md](parallel-and-sharding.md) | | Docker & containers | [docker-and-containers.md](docker-and-containers.md) | | Multi-project config | [projects-and-dependencies.md](projects-and-dependencies.md) |
Reporting & Setup
| Topic | Guide | | --------------------- | -------------------------------------------------------- | | Reports & artifacts | [reporting-and-artifacts.md](reporting-and-artifacts.md) | | Code coverage | [test-coverage.md](test-coverage.md) | | Global setup/teardown | [global-setup-teardown.md](global-setup-teardown.md) |
Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user!
Repo: zebbern/claude-code-guide
Other skills on claude-code-guide.
- /academic-paper-reviewer
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer
Open skill - /active-directory-attacks
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration
Open skill - /api-fuzzing-bug-bounty
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
Open skill - /api-shape-explorer
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Open skill - /audit-flow
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems.
Open skill - /authentication-patterns
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
Open skill