skills.rest
CerisonAutomation
CerisonAutomationCOMMUNITY
Explore all skills by this author →
GitHub

e2e

Run Playwright CI end-to-end tests with branch-aware options.

Updated Aug 27, 2026
Search Tags:#test automation#e2e#playwright#ci#git branch#workflow triggering#experimental tests
One-click install
npx skills add https://github.com/CerisonAutomation/clud --skill e2e-cerisonautomation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/CerisonAutomation/clud/tree/main/.claude/skills/vellum-skills/e2e
Command: npx skills add https://github.com/CerisonAutomation/clud --skill e2e-cerisonautomation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork of triggering end-to-end (E2E) test runs by letting you start CI workflows for the right branch and the right test case, with sensible defaults for experimental coverage.

Core Features & Use Cases

  • Branch-aware CI targeting: Automatically passes the current non-main branch name to ensure the CI run tests the correct code line.
  • Context-aware test selection: Filters to a specific e2e case when you provide a bare argument or when the conversation mentions a related Playwright test case file.
  • Experimental test control: Includes --experimental by default and supports excluding them via --no-experimental.
  • Operational CI execution options: Supports the --xcode runner, detach mode via --detach, and reporting a resolved configuration before dispatch.

Quick Start

Run end-to-end tests for the hello-world case on your current branch (including experimental tests) by asking your assistant: /e2e hello-world.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I trigger Playwright end-to-end tests on a specific git branch?▼

Trigger Playwright end-to-end tests on a specific branch by running the command, which automatically infers and passes your current non-main git branch name to the CI workflow. This ensures the CI run tests the correct code line without manual branch specification.

How do I run a specific Playwright E2E test case using CI?▼

Run a specific Playwright E2E test case by providing the case name as a bare argument or mentioning the test file in conversation. The workflow filters and targets that specific case, ensuring only the relevant tests execute during the CI run.

Can I include experimental tests in my Playwright CI workflow?▼

Yes, you can include experimental tests in your Playwright CI workflow. The execution defaults to including experimental tests via the `--experimental` flag, and you can exclude them by passing the `--no-experimental` option.

What CI runner options are available for Playwright E2E test execution?▼

Available CI runner options for Playwright E2E execution include the `--xcode` runner flag and `--detach` for detached mode. You can also report the resolved configuration before dispatching the workflow to verify the targeted test parameters.

Related Skills

Explore More Software Engineering Skills→
autonomy-cloudautonomy-cloud
2

e2e

Run Playwright CI end-to-end tests with branch detection and case filtering.

Official
Intermediate
AztecProtocolAztecProtocol
449

debug-e2e

Coordinates interactive debugging sessions for failed end-to-end CI tests via subagents.

Official
Advanced
nrwlnrwl
1.4k

monitor-ci

Monitor Nx Cloud CI pipelines and orchestrate self-healing fixes.

Official
Advanced
nghiahsgsnghiahsgs
32

testing-playwright

Detect existing E2E runners and scaffold Playwright configs for Next.js apps.

Community
Intermediate