Agent skill

E2E Verify Fix

by redhat-developer in redhat-developer/rhdh

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

Apache-2.0Auto-check: notesTesting & QA

Install E2E Verify Fix

skills CLI
$ npx skills add redhat-developer/rhdh --skill e2e-verify-fix -a claude-code

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

GitHub CLI
$ gh skill install redhat-developer/rhdh e2e-verify-fix --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-verify-fix .claude/skills/e2e-verify-fix && 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-verify-fix
GitHub stars
172
Token cost
~1.3k tokens
SKILL.md length
514 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 6 steps: Single Run Verification via Healer → Multi-Run Stability Check → Full Project Stability Check → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers When to Use, MANDATORY: Use the Playwright…, Verification Steps and Result Summary
  • Calls yarn, npx and git

What it does

E2E Verify Fix is an agent skill from redhat-developer/rhdh. Verify an E2E test fix by running the test multiple times and checking code quality

Its SKILL.md is about 1.3k 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, Code quality 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 Code quality
  • Tasks that involve Platform engineering

Example prompts

  • “/e2e-verify-fix”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Single Run Verification via Healer
  2. Multi-Run Stability Check
  3. Full Project Stability Check
  4. Code Quality Checks
  5. Optional: Full Project Regression Check
  6. Review the Diff

What it can do on your machine

Read from SKILL.md and the folder at commit ef35b18. 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
    • git

    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 no API keys, tokens, secrets or passwords.

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

Context cost

E2E Verify Fix loads about 1.3k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 514 words of instructions outside code blocks.

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

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:37
    Ensure the `.env` file exists — generate it with `source local-test-setup.sh <showcase|rbac> --env`. To regenerate (e.g.
  • NoteMentions a .env fileSKILL.md:48
    Run: set -a && source .env && set +a && npx playwright test <spec-file> --project=any-test --retries=0 --workers=1 -g '<
  • NoteMentions a .env fileSKILL.md:60
    set -a && source .env && set +a
  • NoteMentions a .env fileSKILL.md:83
    set -a && source .env && set +a

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 ef35b18, republished under its Apache-2.0 licence (© redhat-developer). 514 words, ~1,326 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-verify-fix/SKILL.md (or your agent's skills folder).
name
e2e-verify-fix
description
Verify an E2E test fix by running the test multiple times and checking code quality

Verify Fix

Verify that the test fix works reliably and passes all code quality checks.

When to Use

Use this skill after implementing a fix (via e2e-diagnose-and-fix) to confirm the fix works before submitting a PR.

MANDATORY: Use the Playwright Healer Agent for Verification

Always use the Playwright healer agent for test verification. The healer provides step-by-step debugging if a run fails, making it faster to iterate on fixes.

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 direct test execution for all verification steps (yarn playwright test ...).

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.

Ensure the .env file exists — generate it with source local-test-setup.sh <showcase|rbac> --env. To regenerate (e.g. after token expiry), re-run the same command.

Verification Steps

1. Single Run Verification via Healer

Invoke the healer agent to run the fixed test once:

Task: "You are the Playwright Test Healer agent. Verify a fix by running the test once.
Working directory: <path>/e2e-tests
Run: set -a && source .env && set +a && npx playwright test <spec-file> --project=any-test --retries=0 --workers=1 -g '<test-name>'
If it passes, report success. If it fails, examine the error and report what went wrong."

If it fails, go back to e2e-diagnose-and-fix and iterate — use the healer agent there too for the fix.

2. Multi-Run Stability Check

Run the test 5 times consecutively to verify no flakiness was introduced:

bash
cd e2e-tests
set -a && source .env && set +a
PASS=0; FAIL=0
for i in $(seq 1 5); do
  echo "=== Stability run $i/5 ==="
  if npx playwright test <spec-file> --project=any-test --retries=0 --workers=1 2>&1; then
    PASS=$((PASS + 1))
  else
    FAIL=$((FAIL + 1))
  fi
done
echo "Stability results: $PASS/5 passed"

Acceptance criteria: 5/5 passes. If any run fails, invoke the healer agent on the failing run to diagnose and fix the remaining issue — do not manually guess at fixes.

Show full SKILL.md (267 more words)Show less
3. Full Project Stability Check

When to run: This step is required if the failure was only reproducible when running the full CI project (CI=true yarn playwright test --project=<ci-project>) during e2e-reproduce-failure. If the failure reproduced in isolated single-test runs, this step is optional but still recommended.

Run the full project to confirm the fix holds under CI-like concurrency:

bash
cd e2e-tests
set -a && source .env && set +a
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 verifies the fix under the same worker count and test interaction conditions that triggered the original failure.

Acceptance criteria: The full project run must pass. If the fixed test still fails when run alongside other tests, the fix is incomplete — return to e2e-diagnose-and-fix.

IMPORTANT: Never skip verification steps. If you cannot run tests (e.g., no cluster available, environment issues), stop and ask the user for explicit approval before proceeding without verification. Do not assume it's OK to skip.

4. Code Quality Checks

Run all code quality checks in the e2e-tests workspace:

bash
cd e2e-tests

# TypeScript compilation
yarn tsc:check

# ESLint
yarn lint:check

# Prettier formatting
yarn prettier:check

Fix any issues found:

bash
# Auto-fix lint issues
yarn lint:fix

# Auto-fix formatting
yarn prettier:fix
5. Optional: Full Project Regression Check

If the fix touches shared utilities or page objects, run the entire Playwright project to check for regressions:

bash
cd e2e-tests
yarn playwright test --project=<project> --retries=0

This is optional for isolated spec file changes but recommended for changes to:

  • e2e-tests/playwright/utils/ (utility classes)
  • e2e-tests/playwright/support/ (page objects, selectors)
  • e2e-tests/playwright/data/ (shared test data)
  • playwright.config.ts (configuration)
6. Review the Diff

Before submitting, review all changes:

bash
git diff
git diff --stat

Verify:

  • Only intended files were changed
  • No secrets or credentials were added
  • No unrelated changes were included
  • Component annotations are present in any new/modified spec files
  • Semantic selectors are used (no deprecated CSS class selectors)

Result Summary

After verification, produce a summary:

Fix Verification Results:
- Test: <spec-file> (<project>)
- Single run: PASS
- Stability (5 runs): 5/5 PASS
- TypeScript: PASS
- ESLint: PASS
- Prettier: PASS
- Files changed: <list>
- Ready for PR: YES/NO

© 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-verify-fix of redhat-developer/rhdh.

Open the folder on GitHubat commit ef35b18

Compare with similar skills

E2E Verify Fix 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 Verify Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Verify Fix this skillredhat-developer/rhdh172—~1.3kAutomated safety check: NotesApache-2.0
Hydra Devstreamband/hydra-srt146—~995Automated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.3k23 repos~2.8kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence

Similar skills

  • Hydra Dev

    streamband/hydra-srt

    Run HydraSRT development workflows: mix q quality gate, Elixir unit/E2E tests, native Rust tests, web Vitest/Playwright, and make dev.

    146 GitHub stars~995 tokensUpdated 21 days ago
    Testing & QAAuto-check passed
  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • 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
  • E2E Testing

    langflow-ai/langflow

    Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.

    156k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed
  • E2E Reproduce Failure

    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

    172 GitHub stars~1.9k tokensUpdated yesterday
    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 yesterday
    Auto-check passed

Works with

Categories

Questions about E2E Verify Fix

What does E2E Verify Fix do?

Verify an E2E test fix by running the test multiple times and checking code quality. E2E Verify Fix is an agent skill from redhat-developer/rhdh.

When should I use E2E Verify Fix?

E2E Verify Fix fits situations like: tasks that involve End-to-end testing; tasks that involve Code quality; tasks that involve Platform engineering.

How do I install E2E Verify Fix in Claude Code?

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

How do I install E2E Verify Fix in Codex?

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

Can I use E2E Verify Fix 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-verify-fix -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-verify-fix, .gemini/skills/e2e-verify-fix, .github/skills/e2e-verify-fix and .opencode/skills/e2e-verify-fix in your project.

What does E2E Verify Fix need to run?

Going by SKILL.md and its folder, E2E Verify Fix needs the command-line tools its instructions call (yarn, npx and git). Our summary lists: Node.js.

Does E2E Verify Fix 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 Verify Fix 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 Verify Fix use?

E2E Verify Fix 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 Verify Fix use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Verify Fix?

Skills that share tags, products or a category with E2E Verify Fix: Hydra Dev (streamband/hydra-srt, 146 stars), Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.3k stars) and Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Verify Fix?

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 6, 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.