Debug Playwright
quay/quay
Debug Playwright E2E test failures from GitHub Actions CI runs.
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Install Cucumber and Playwright E2E Tests
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langgenius/dify e2e-cucumber-playwright --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .claude/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.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/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .claude/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwrightType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langgenius/dify e2e-cucumber-playwright --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .agents/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .agents/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langgenius/dify e2e-cucumber-playwright --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .cursor/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .cursor/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langgenius/dify.git --path .agents/skills/e2e-cucumber-playwright--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langgenius/dify e2e-cucumber-playwright --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .gemini/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .gemini/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langgenius/dify e2e-cucumber-playwrightInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .github/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .github/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill e2e-cucumber-playwright -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langgenius/dify e2e-cucumber-playwright --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/e2e-cucumber-playwright .opencode/skills/e2e-cucumber-playwright && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "e2e-cucumber-playwright" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/e2e-cucumber-playwright into .opencode/skills/e2e-cucumber-playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-cucumber-playwright", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
e2e-cucumber-playwright- GitHub stars
- 158k
- Token cost
- ~682 tokens
- SKILL.md length
- 303 words
- Files
- 4 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
- Works in 6 steps: Add E2E coverage only for a critical… → Identify the user-visible behavior and… → Read the target scenario, matching step… → …
- Adding a scenario for a critical user journey to the E2E suite
- SKILL.md covers Topic Routing and Workflow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill is for work inside one repository's `e2e/` folder. It defers to the suite's own `e2e/AGENTS.md`, and to any feature-level `AGENTS.md` nearby, for architecture, commands, tags and cleanup rules, and adds no separate policy. Cucumber runs scenarios, hooks and reporting; Playwright supplies the browser, pages, locators, actions and assertions. Their timeouts stay separate, and importing from `@playwright/test` does not bring in the Playwright Test runner's configuration, fixtures or retries.
Two bundled references are read only when a change needs them: one on Playwright locators, assertions, isolation and waiting, and one on Cucumber scenario wording, step granularity, expressions, World state, hooks and tag design. The workflow adds E2E coverage only for a critical user journey that cheaper tests do not already prove, reuses an existing step when wording and behavior match, keeps setup and cleanup with their owners and runs the narrowest tagged scenario first. Reviews lead with reproducible failures and flake sources. It is not meant for Vitest, React Testing Library, backend tests or general browser automation.
When your agent uses it
- Adding a scenario for a critical user journey to the E2E suite
- Reviewing a pull request that changes feature files or step definitions
- Fixing a flaky locator or assertion in a Playwright step
- Choosing tags and step wording for a new Cucumber scenario
Example prompts
- “Add an E2E scenario for the login flow and reuse the existing steps where they fit.”
- “Review this change to the step definitions for flake risks and locator choices.”
- “The checkout scenario times out sometimes, so look at how the wait is written.”
- “Which Cucumber tag should the new profile scenario get?”
Requirements
- The repository's `e2e/` suite with Cucumber and Playwright set up
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Add E2E coverage only for a critical user journey with a cross-boundary outcome that cheaper owner-level tests do not already prove.
- Identify the user-visible behavior and its feature owner. Start from real product defaults and actor roles; setup may establish…
- Read the target scenario, matching step definitions, and lifecycle files only when session or shared state matters.
- Reuse an existing step when wording and behavior match; add one coherent scenario or step when they do not.
- Keep browser actions and assertions at the public user boundary; keep setup, seed, polling, and cleanup at their package-defined owners.
- For changes, run the narrowest tagged scenario and package checks documented in e2e/AGENTS.md; broaden only for shared hooks, tags, or…
What it can do on your machine
Read from SKILL.md and the folder at commit cecdb28. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Cucumber and Playwright E2E Tests loads about 682 tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 303 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 303 words (~682 tokens).
“e2e/AGENTS.md owns the suite architecture, lifecycle, commands, tags, generated-client boundaries, fixtures, and cleanup contracts. Read the nearest feature-scoped AGENTS.md when one exists. This skill adds no parallel package policy.”
- name
- e2e-cucumber-playwright
Files
SKILL.md and 3 other files (references) in .agents/skills/e2e-cucumber-playwright of langgenius/dify.
- SKILL.md
- agents/openai.yaml
- references/cucumber-best-practices.md
- references/playwright-best-practices.md
Open the folder on GitHubat commit cecdb28
Compare with similar skills
Cucumber and Playwright E2E Tests 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cucumber and Playwright E2E Tests this skilllanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence | |
| Debug Playwrightquay/quay | 2.8k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.1k | Automated safety check: Pass | None | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| E2Esendou-ink/sendou.ink | 297 | — | ~2.1k | Automated safety check: Notes | AGPL-3.0 | |
| Hardening Flaky E2E TestsComfy-Org/ComfyUI_frontend | 2.1k | — | ~2.8k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
E2E
sendou-ink/sendou.ink
Run, debug, and manage Playwright e2e tests. An agent skill from sendou-ink/sendou.ink.
Hardening Flaky E2E Tests
Comfy-Org/ComfyUI_frontend
Diagnoses and fixes flaky Playwright e2e tests by replacing race-prone patterns with retry-safe alternatives.
Playwright Expert
cin12211/orca-q
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.
More from langgenius/dify
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
Frontend Code Review
langgenius/dify
Reviews frontend changes under `web/` or `packages/dify-ui/` for concrete defects and broken project contracts, using routed rule packs and a severity scale for findings.
Dify Component Writing Guide
langgenius/dify
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data…
Dify Command Line with difyctl
langgenius/dify
Base skill for the difyctl CLI: discover a Dify server's operations through help output and run them as commands, always with JSON output.
Dify Frontend Testing
langgenius/dify
Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test…
Related
Works with
Categories
Questions about Cucumber and Playwright E2E Tests
What does Cucumber and Playwright E2E Tests do?
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions. This skill is for work inside one repository's `e2e/` folder.md` nearby, for architecture, commands, tags and cleanup rules, and adds no separate policy.
When should I use Cucumber and Playwright E2E Tests?
Cucumber and Playwright E2E Tests fits situations like: adding a scenario for a critical user journey to the E2E suite; reviewing a pull request that changes feature files or step definitions; fixing a flaky locator or assertion in a Playwright step; choosing tags and step wording for a new Cucumber scenario.
How do I install Cucumber and Playwright E2E Tests in Claude Code?
Run `npx skills add langgenius/dify --skill e2e-cucumber-playwright -a claude-code`. Or copy the skill folder (.agents/skills/e2e-cucumber-playwright in langgenius/dify) into .claude/skills/e2e-cucumber-playwright in your project. Claude Code loads it when a task matches its description.
How do I install Cucumber and Playwright E2E Tests in Codex?
Run `npx skills add langgenius/dify --skill e2e-cucumber-playwright -a codex`. Or copy the skill folder (.agents/skills/e2e-cucumber-playwright in langgenius/dify) into .agents/skills/e2e-cucumber-playwright in your project. Codex loads it when a task matches its description.
Can I use Cucumber and Playwright E2E Tests 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 langgenius/dify --skill e2e-cucumber-playwright -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/e2e-cucumber-playwright, .gemini/skills/e2e-cucumber-playwright, .github/skills/e2e-cucumber-playwright and .opencode/skills/e2e-cucumber-playwright in your project.
What does Cucumber and Playwright E2E Tests need to run?
SKILL.md names no scripts, command-line tools or credentials: Cucumber and Playwright E2E Tests is instructions for the agent only. Our summary lists: The repository's `e2e/` suite with Cucumber and Playwright set up.
Does Cucumber and Playwright E2E Tests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cucumber and Playwright E2E Tests 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 Cucumber and Playwright E2E Tests use?
Cucumber and Playwright E2E Tests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Cucumber and Playwright E2E Tests use?
About 682 tokens (SKILL.md is roughly 2.7k 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 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Cucumber and Playwright E2E Tests?
Skills that share tags, products or a category with Cucumber and Playwright E2E Tests: Debug Playwright (quay/quay, 2.8k stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars) and E2E (sendou-ink/sendou.ink, 297 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cucumber and Playwright E2E Tests?
langgenius (a GitHub organization) maintains it in langgenius/dify, which has 158,055 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: langgenius/dify on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.