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

Fix E2E Tests

by platformplatform in platformplatform/PlatformPlatform

Systematically fix all failing E2E tests using a phased diagnostic approach.

MITAuto-check: notesTesting & QA

Install Fix E2E Tests

skills CLI
$ npx skills add platformplatform/PlatformPlatform --skill fix-e2e-tests -a claude-code

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

GitHub CLI
$ gh skill install platformplatform/PlatformPlatform fix-e2e-tests --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/platformplatform/PlatformPlatform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-e2e-tests .claude/skills/fix-e2e-tests && 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
fix-e2e-tests
GitHub stars
441
Token cost
~1.2k tokens
SKILL.md length
728 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Systematically fix all failing E2E tests using a phased diagnostic approach.

  • Works in 7 steps: Diagnostic Run -- Smoke Tests in Chromium → Fix Permanently Failing Tests → Address Flaky Tests → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers Core Principles, STEP 1: Diagnostic Run --…, STEP 2: Fix Permanently… and STEP 3: Address Flaky Tests, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fix E2E Tests is an agent skill from platformplatform/PlatformPlatform. Systematically fix all failing E2E tests using a phased diagnostic approach. Classifies tests as passing, flaky, or permanently failing, then fixes them one by one with progressive scope expansion.

Its SKILL.md is about 1.2k 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 and Failing and flaky tests. The repository describes itself as: A platform designed for building enterprise-grade, multi-tenant products using Azure, .NET, React, TypeScript, Infrastructure as Code, etc. The licence is MIT.

When your agent uses it

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

Example prompts

  • “/fix-e2e-tests”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep

Workflow steps

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

  1. Diagnostic Run -- Smoke Tests in Chromium
  2. Fix Permanently Failing Tests
  3. Address Flaky Tests
  4. Expand to All Browsers -- Smoke Tests
  5. Expand to All Tests in Chromium
  6. Expand to All Tests in All Browsers
  7. Final Validation

What it can do on your machine

Read from SKILL.md and the folder at commit 269de1c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep

    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

Fix E2E Tests loads about 1.2k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 728 words of instructions outside code blocks.

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

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.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep

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 platformplatform/PlatformPlatform at commit 269de1c, republished under its MIT licence (© platformplatform). 728 words, ~1,194 tokens.

Download SKILL.mdSave it as .claude/skills/fix-e2e-tests/SKILL.md (or your agent's skills folder).
name
fix-e2e-tests
description
Systematically fix all failing E2E tests using a phased diagnostic approach. Classifies tests as passing, flaky, or permanently failing, then fixes them one by one with progressive scope expansion.
allowed-tools
Read, Write, Edit, Bash, Glob, Grep

Fix E2E Tests

Systematically fix all failing end-to-end tests by diagnosing first, then fixing one by one, expanding scope progressively. Optimizes for speed of fixing over exhaustive analysis.

Core Principles

  1. Test bug or app bug? For every failure, critically evaluate: is the test wrong, or is the application wrong? A failing test might be correctly catching an application bug. If the application is broken, fix the application -- do not make the test pass by weakening it
  2. Focus on the first failing step only. Do not attempt to fix later steps in a test until the first step passes. You do not know if later steps would actually fail
  3. Never predict failures. Do not speculatively fix things that look like they might fail. Only fix what is actually failing right now
  4. Apply global fixes. When a fix applies across multiple tests (e.g., a renamed button), apply it everywhere before re-running. Do not fix one test at a time when the same change applies to many
  5. One test at a time. After global fixes, run each failing test individually. Fix the first step. Re-run. Iterate

STEP 1: Diagnostic Run -- Smoke Tests in Chromium

Run all smoke tests in Chromium with retries=1 to classify every test:

  • Passing: Passes on first attempt
  • Flaky: Fails first attempt, passes on retry
  • Permanently failing: Fails both attempts

Save a diagnostic report to .workspace/{branch-name}/e2e-diagnostic.md with test counts and, for each failure, the test file, test name, first failing step, and error message.

If all tests pass, skip to STEP 4.

STEP 2: Fix Permanently Failing Tests

Work through permanently failing tests one at a time:

  1. Run the failing test in isolation to confirm it is truly permanently failing and not flaky. A test that failed in the full suite might pass when run alone (resource contention, test ordering). If it passes in isolation, reclassify it as flaky and handle in STEP 3
  2. Read the first failing step and its error message
  3. Evaluate: test bug or app bug? Did we deliberately change something the test is catching? Would a real user see this as broken? If it is an app bug, report it and move on -- do not fix the test
  4. Check for global applicability. Does the same fix apply to other tests? Apply globally first, then re-run diagnostics
  5. Fix the first step. Make the minimal change. Do not touch later steps
  6. Re-run the individual test. If it passes, move to the next failing test. If a new step fails, repeat from step 1

Update the diagnostic report after each fix.

Show full SKILL.md (295 more words)Show less

STEP 3: Address Flaky Tests

After permanently failing tests are fixed:

  1. Run each flaky test multiple times individually to confirm flakiness
  2. Identify the root cause -- do not add arbitrary waits or timeouts
  3. Review the E2E test rules in .claude/rules/end-to-end-tests/ for known patterns
  4. Fix the root cause. If the flakiness is caused by an application bug, report it to the user -- the application must be fixed
  5. Re-run the test multiple times to confirm it is now stable. Do not move on until it passes consistently

STEP 4: Expand to All Browsers -- Smoke Tests

Run smoke tests across all browsers. Fix any browser-specific failures using the same one-at-a-time process from STEP 2.

STEP 5: Expand to All Tests in Chromium

Run all tests (smoke + comprehensive, excluding slow) in Chromium. Fix any failures using the same process.

STEP 6: Expand to All Tests in All Browsers

Run the full test suite across all browsers. Fix any remaining failures.

STEP 7: Final Validation

Run the full test suite across all browsers one final time. Every test must pass. Zero failures, zero flaky tests. This skill is not complete until all tests pass consistently.

Update .workspace/{branch-name}/e2e-diagnostic.md with:

  • Final test counts: all must be passing
  • Summary of changes made (test fixes and application fixes)
  • Application bugs that were found and fixed

Key Rules

  • Run tests for the specific failing file, not the whole suite, when fixing individual tests
  • Apply global fixes before re-running diagnostics
  • Do not run all browsers until Chromium passes
  • Only fix what is actually failing -- do not refactor passing tests
  • Read .claude/rules/end-to-end-tests/ before making changes
  • If stuck after 3 fix attempts on the same test, escalate to the user
  • Zero tolerance: this skill is not complete until every test passes in every browser

© platformplatform, MIT. 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/fix-e2e-tests of platformplatform/PlatformPlatform.

Open the folder on GitHubat commit 269de1c

Compare with similar skills

Fix 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.

Fix E2E Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix E2E Tests this skillplatformplatform/PlatformPlatform441—~1.2kAutomated safety check: NotesMIT
Openspec Plus TDDelastic/terraform-provider-elasticstack2101 repos~4.7kAutomated safety check: PassApache-2.0
Swarm CI MonitorZaxbyHub/opencode-swarm490—~4.9kAutomated safety check: PassMIT
Mobile App Testingsecondsky/claude-skills227—~643Automated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
Debugging Opik E2E Testscomet-ml/opik22k—~1.8kAutomated safety check: PassApache-2.0

Similar skills

  • Openspec Plus TDD

    elastic/terraform-provider-elasticstack

    Official

    MANDATORY skill that activates whenever code is written to implement an OpenSpec change task.

    210 GitHub starsUsed in 1 repo~4.7k tokens
    Testing & QAAuto-check passed

  • Swarm CI Monitor

    ZaxbyHub/opencode-swarm

    End-to-end CI monitor that takes an already-human-reviewed PR, exhaustively researches every CI failure, fixes it end-to-end, iterates until all required checks are green (max 5 fix cycles), then…

    490 GitHub stars~4.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Mobile App Testing

    secondsky/claude-skills

    Mobile app testing with unit tests, UI automation, performance testing.

    227 GitHub stars~643 tokensUpdated 9 days ago
    Testing & QAAuto-check passed

  • 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

  • Codex Local CLI E2E

    rebornix/Agmente

    Run and debug Agmente iOS end-to-end tests against a real local Codex CLI app-server instance.

    545 GitHub stars~625 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

More from platformplatform/PlatformPlatform

All 18 skills in this repo

  • Create Prd

    platformplatform/PlatformPlatform

    Create a product requirement document (PRD) for a new feature.

    441 GitHub stars~3k tokensUpdated 13 days ago
    Auto-check passed

  • Rebuild Branch

    platformplatform/PlatformPlatform

    Rebuild a stale branch by cherry-picking each commit onto a fresh branch off main, using a ralph-loop to validate each commit (build, test, format, lint, optional e2e) before moving on.

    441 GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check: notes

  • Swc Plugin Compatibility

    platformplatform/PlatformPlatform

    Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes.

    441 GitHub stars~873 tokensUpdated 13 days ago
    Auto-check passed

  • Aspire Restart

    platformplatform/PlatformPlatform

    Start or restart the .NET Aspire AppHost via the developer CLI.

    441 GitHub stars~415 tokensUpdated 13 days ago
    Auto-check passed

  • Commit

    platformplatform/PlatformPlatform

    Commit session changes to git. An agent skill from platformplatform/PlatformPlatform.

    441 GitHub stars~567 tokensUpdated 13 days ago
    Auto-check passed

  • E2E

    platformplatform/PlatformPlatform

    Run end-to-end Playwright tests via the developer CLI. An agent skill from platformplatform/PlatformPlatform.

    441 GitHub stars~542 tokensUpdated 13 days ago
    Auto-check passed

Categories

Questions about Fix E2E Tests

What does Fix E2E Tests do?

Systematically fix all failing E2E tests using a phased diagnostic approach. Fix E2E Tests is an agent skill from platformplatform/PlatformPlatform. Systematically fix all failing E2E tests using a phased diagnostic approach.

When should I use Fix E2E Tests?

Fix E2E Tests fits situations like: tasks that involve End-to-end testing; tasks that involve Failing and flaky tests.

How do I install Fix E2E Tests in Claude Code?

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

How do I install Fix E2E Tests in Codex?

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

Can I use Fix 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 platformplatform/PlatformPlatform --skill fix-e2e-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-e2e-tests, .gemini/skills/fix-e2e-tests, .github/skills/fix-e2e-tests and .opencode/skills/fix-e2e-tests in your project.

What does Fix E2E Tests need to run?

SKILL.md names no scripts, command-line tools or credentials: Fix E2E Tests is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.

Does Fix 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 Fix E2E Tests safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Fix E2E Tests use?

Fix E2E Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix E2E Tests use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Fix E2E Tests?

Skills that share tags, products or a category with Fix E2E Tests: Openspec Plus TDD (elastic/terraform-provider-elasticstack, 210 stars), Swarm CI Monitor (ZaxbyHub/opencode-swarm, 490 stars), Mobile App Testing (secondsky/claude-skills, 227 stars) and Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix E2E Tests?

platformplatform (a GitHub organization) maintains it in platformplatform/PlatformPlatform, which has 441 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 24, 2026.

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