New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

E2E Reproduce Failure

by redhat-developer in redhat-developer/rhdh

Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky

Apache-2.0Auto-check: notesTesting & QA

Install E2E Reproduce Failure

skills CLI
$ npx skills add redhat-developer/rhdh --skill e2e-reproduce-failure -a claude-code

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

GitHub CLI
$ gh skill install redhat-developer/rhdh e2e-reproduce-failure --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/redhat-developer/rhdh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/e2e-reproduce-failure .claude/skills/e2e-reproduce-failure && 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
e2e-reproduce-failure
GitHub stars
172
Token cost
~1.9k tokens
SKILL.md length
652 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky

  • Tasks that involve End-to-end testing
  • SKILL.md covers When to Use, Prerequisites, Environment Setup and MANDATORY: Use the Playwright…, plus 4 more sections
  • Calls yarn, npx and curl; needs K8S_CLUSTER_TOKEN
  • Tasks that involve Failing and flaky tests

What it does

E2E Reproduce Failure is an agent skill from redhat-developer/rhdh. Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing, Failing and flaky tests and Platform engineering. It works with Playwright. The repository describes itself as: The repo formerly known as janus-idp/backstage-showcase. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve End-to-end testing
  • Tasks that involve Failing and flaky tests
  • Tasks that involve Platform engineering

Example prompts

  • “/e2e-reproduce-failure”

Requirements

  • Node.js
  • A credential in K8S_CLUSTER_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit e51f3cf. 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:

    • yarn
    • npx
    • curl

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

  • Network

    Links to these hosts (documentation or services it may open):

    • playwright.dev

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • K8S_CLUSTER_TOKEN

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

Context cost

E2E Reproduce Failure loads about 1.9k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 652 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:67
    Generate the `.env` file by passing the `--env` flag to `local-test-setup.sh`:
  • NoteMentions a .env fileSKILL.md:92
    Run: set -a && source .env && set +a && npx playwright test <spec-file> --project=any-test --retries=0 --workers=1 -g '<

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 redhat-developer/rhdh at commit e51f3cf, republished under its Apache-2.0 licence (© redhat-developer). 652 words, ~1,867 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-reproduce-failure/SKILL.md (or your agent's skills folder).
name
e2e-reproduce-failure
description
Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky

Reproduce Failure

Run the failing test locally against a deployed RHDH instance to confirm the failure and classify it.

When to Use

Use this skill after deploying RHDH (via e2e-deploy-rhdh) when you need to verify the test failure reproduces locally before attempting a fix.

Prerequisites

  • RHDH deployed and accessible (BASE_URL set)
  • Environment configured via source e2e-tests/local-test-setup.sh <showcase|rbac>
  • Node.js 22 and Yarn available
  • Playwright browsers installed (cd e2e-tests && yarn install && yarn playwright install chromium)

Environment Setup

Source the Test Environment
bash
# For non-RBAC tests (showcase, showcase-k8s, showcase-operator, etc.)
source e2e-tests/local-test-setup.sh showcase

# For RBAC tests (showcase-rbac, showcase-rbac-k8s, showcase-operator-rbac)
source e2e-tests/local-test-setup.sh rbac

This exports all required environment variables: BASE_URL, K8S_CLUSTER_URL, K8S_CLUSTER_TOKEN, and all Vault secrets.

Verify Environment
bash
echo "BASE_URL: $BASE_URL"
curl -sSk "$BASE_URL" -o /dev/null -w "HTTP Status: %{http_code}\n"

MANDATORY: Use the Playwright Healer Agent for Reproduction

Always use the Playwright healer agent to run and reproduce failing tests. The healer provides richer diagnostics than plain yarn playwright test — it can debug step-by-step, inspect the live UI, and collect detailed failure context automatically.

Note: The Playwright healer agent is currently supported in OpenCode and Claude Code only. In Cursor or other tools without Playwright agent support, skip the healer initialization and use the "Fallback: Direct Execution" method below instead.

Healer Initialization

If not already initialized in this session, initialize the healer agent in e2e-tests/:

bash
cd e2e-tests

# For OpenCode
npx playwright init-agents --loop=opencode

# For Claude Code
npx playwright init-agents --loop=claude

See https://playwright.dev/docs/test-agents for the full list of supported tools and options. The generated files are local tooling — do NOT commit them.

Environment Setup

Generate the .env file by passing the --env flag to local-test-setup.sh:

bash
cd e2e-tests
source local-test-setup.sh <showcase|rbac> --env

To regenerate (e.g. after token expiry), re-run the command above.

Project Selection

When running specific test files or test cases, use --project=any-test to avoid running the smoke test dependency. The any-test project matches any spec file without extra overhead:

bash
yarn playwright test <spec-file> --project=any-test --retries=0 --workers=1
Running via Healer Agent

Invoke the healer agent via the Task tool:

Task: "You are the Playwright Test Healer agent. Run the following test to reproduce a CI failure.
Working directory: <path>/e2e-tests
Test: <spec-file> --project=any-test -g '<test-name>'
Run: set -a && source .env && set +a && npx playwright test <spec-file> --project=any-test --retries=0 --workers=1 -g '<test-name>'
If the test fails, examine the error output, screenshots in test-results/, and error-context.md.
Report: pass/fail, exact error message, what the UI shows at the point of failure."
Fallback: Direct Execution

If the healer agent is unavailable (e.g., in Cursor), run tests directly:

bash
cd e2e-tests
yarn playwright test <spec-file> --project=any-test --retries=0 --workers=1

Examples:

bash
# A specific spec file
yarn playwright test playwright/e2e/plugins/topology/topology.spec.ts --project=any-test --retries=0 --workers=1

# A specific test by name
yarn playwright test -g "should display topology" --project=any-test --retries=0 --workers=1
Headed / Debug Mode

For visual debugging when manual investigation is needed:

bash
# Headed mode (visible browser)
yarn playwright test <spec-file> --project=any-test --retries=0 --workers=1 --headed

# Debug mode (Playwright Inspector, step-by-step)
yarn playwright test <spec-file> --project=any-test --retries=0 --workers=1 --debug

Flakiness Detection

If the first run passes (doesn't reproduce the failure), run multiple times to check for flakiness:

bash
cd e2e-tests

# Run 10 times and track results
PASS=0; FAIL=0
for i in $(seq 1 10); do
  echo "=== Run $i ==="
  if yarn playwright test <spec-file> --project=any-test --retries=0 --workers=1 2>&1; then
    PASS=$((PASS + 1))
  else
    FAIL=$((FAIL + 1))
  fi
done
echo "Results: $PASS passed, $FAIL failed out of 10 runs"

Result Classification

Consistent Failure
  • Definition: Fails every time (10/10 runs fail)
  • Action: Proceed to e2e-diagnose-and-fix skill
  • Confidence: High — the fix can be verified reliably
Flaky
  • Definition: Fails some runs but not all (e.g., 3/10 fail)
  • Action: Proceed to e2e-diagnose-and-fix skill, focus on reliability improvements
  • Typical causes: Race conditions, timing dependencies, state leaks between tests, external service variability
Show full SKILL.md (285 more words)Show less
Cannot Reproduce
  • Definition: Passes all runs locally (0/10 fail)
  • Before giving up, try running the entire Playwright project that failed in CI with CI=true to simulate CI conditions (this sets the worker count to 3, matching CI):
    bash
    cd e2e-tests
CI=true yarn playwright test --project=<ci-project> --retries=0
    Replace <ci-project> with the project from the CI failure (e.g., showcase, showcase-rbac). This runs all tests in that project concurrently, which can expose race conditions and resource contention that single-test runs miss.
  • If the full project run also passes, stop and ask the user for approval before skipping this step. Present the reproduction results and the list of possible environment differences. Do not proceed to diagnose-and-fix without explicit user confirmation.
  • Investigation: Check environment differences between local and CI:
    • Cluster version: CI may use a different OCP version (check the cluster pool version)
    • Image version: CI may use a different RHDH image
    • Resource constraints: CI clusters may have less resources
    • Parallel execution: CI runs with 3 workers; the full project run above simulates this
    • Network: CI clusters are in us-east-2 AWS region
    • External services: GitHub API rate limits, Keycloak availability

Artifact Collection

Playwright Traces

After a test failure, traces are saved in e2e-tests/test-results/:

bash
# View a trace
yarn playwright show-trace test-results/<test-path>/trace.zip
HTML Report

Never use yarn playwright show-report — it starts a blocking HTTP server that will hang the session. Instead, the HTML report is generated automatically in playwright-report/ after test runs. To view it, open playwright-report/index.html directly in a browser, or use Playwright MCP to navigate to it.

Screenshots and Videos

On failure, screenshots and videos are saved in test-results/<test-path>/:

  • test-failed-1.png — Screenshot at failure point
  • video.webm — Full test recording (if video is enabled)

Test Project Reference

Refer to the e2e-fix-workflow rule for the Playwright project → config map mapping.

© redhat-developer, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/e2e-reproduce-failure of redhat-developer/rhdh.

Open the folder on GitHubat commit e51f3cf

Compare with similar skills

E2E Reproduce Failure 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.

E2E Reproduce Failure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Reproduce Failure this skillredhat-developer/rhdh172—~1.9kAutomated safety check: NotesApache-2.0
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
Debugging Opik E2E Testscomet-ml/opik22k—~1.8kAutomated safety check: PassApache-2.0
Debug Playwrightquay/quay2.8k—~1.2kAutomated safety check: PassApache-2.0
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
Playwright Testingchongdashu/vibejam-starter-pack149—~2.2kAutomated safety check: PassNone

Similar skills

  • Cucumber and Playwright E2E Tests

    langgenius/dify

    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.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed

  • Debugging Opik E2E Tests

    comet-ml/opik

    Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.

    22k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Debug Playwright

    quay/quay

    Debug Playwright E2E test failures from GitHub Actions CI runs.

    2.8k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • E2E

    sendou-ink/sendou.ink

    Run, debug, and manage Playwright e2e tests. An agent skill from sendou-ink/sendou.ink.

    297 GitHub stars~2.1k tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from redhat-developer/rhdh

  • E2E Submit And Review

    redhat-developer/rhdh

    Create a PR for an E2E test fix, trigger Qodo agentic review, address review comments, and monitor CI results

    172 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

  • E2E Deploy Rhdh

    redhat-developer/rhdh

    Deploy RHDH to an OpenShift cluster using local-run.sh for E2E test execution, with autonomous error recovery for deployment failures

    172 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • E2E Diagnose And Fix

    redhat-developer/rhdh

    Analyze a failing E2E test, determine root cause, and fix it using Playwright Test Agents and RHDH project conventions

    172 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes

  • E2E Parse CI Failure

    redhat-developer/rhdh

    Parse a Prow CI job URL or Jira ticket to extract E2E test failure details including test name, spec file, release branch, platform, and error messages

    172 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • E2E Verify Fix

    redhat-developer/rhdh

    Verify an E2E test fix by running the test multiple times and checking code quality

    172 GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Patch Backstage

    redhat-developer/rhdh

    Workflow to backport Backstage changes into RHDH by syncing a downstream maintenance branch and generating yarn patches.

    172 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about E2E Reproduce Failure

What does E2E Reproduce Failure do?

Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky. E2E Reproduce Failure is an agent skill from redhat-developer/rhdh.

When should I use E2E Reproduce Failure?

E2E Reproduce Failure fits situations like: tasks that involve End-to-end testing; tasks that involve Failing and flaky tests; tasks that involve Platform engineering.

How do I install E2E Reproduce Failure in Claude Code?

Run `npx skills add redhat-developer/rhdh --skill e2e-reproduce-failure -a claude-code`. Or copy the skill folder (.claude/skills/e2e-reproduce-failure in redhat-developer/rhdh) into .claude/skills/e2e-reproduce-failure in your project. Claude Code loads it when a task matches its description.

How do I install E2E Reproduce Failure in Codex?

Run `npx skills add redhat-developer/rhdh --skill e2e-reproduce-failure -a codex`. Or copy the skill folder (.claude/skills/e2e-reproduce-failure in redhat-developer/rhdh) into .agents/skills/e2e-reproduce-failure in your project. Codex loads it when a task matches its description.

Can I use E2E Reproduce Failure 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 redhat-developer/rhdh --skill e2e-reproduce-failure -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-reproduce-failure, .gemini/skills/e2e-reproduce-failure, .github/skills/e2e-reproduce-failure and .opencode/skills/e2e-reproduce-failure in your project.

What does E2E Reproduce Failure need to run?

Going by SKILL.md and its folder, E2E Reproduce Failure needs the command-line tools its instructions call (yarn, npx and curl) and credentials named K8S_CLUSTER_TOKEN. Our summary lists: Node.js; A credential in K8S_CLUSTER_TOKEN.

Does E2E Reproduce Failure access the network?

SKILL.md names 1 domain. As links in the text: playwright.dev. This is read from the text; nothing was executed.

Is E2E Reproduce Failure safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does E2E Reproduce Failure use?

E2E Reproduce Failure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does E2E Reproduce Failure use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to E2E Reproduce Failure?

Skills that share tags, products or a category with E2E Reproduce Failure: Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars), Debugging Opik E2E Tests (comet-ml/opik, 22k stars), Debug Playwright (quay/quay, 2.8k stars) and Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Reproduce Failure?

redhat-developer (a GitHub organization) maintains it in redhat-developer/rhdh, which has 172 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.

Source: redhat-developer/rhdh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.