Skip to content
Get packs

End-to-End Testing Reviewer

Reviews a project's end-to-end test coverage and CI enforcement for critical user journeys.

Source Download skill
Repository
thedaviddias/Front-End-Checklist
Stars
74,632
Licence
MIT
Files
2 files

What it does

When installed, the agent checks a codebase for end-to-end tests that cover key user paths such as sign-in, checkout and form submission, and whether those tests run automatically in CI and block merges on failure. It also suggests fixes using Playwright or Cypress and explains good practices like stable selectors and the Page Object Model. It is guidance-driven: the skill is a set of instructions plus a reference document, not a tool that runs tests itself.

Great for

  • Front-end or full-stack teams who want to verify their E2E coverage is actually enforced in CI
  • Developers adding Playwright or Cypress tests to an existing project for the first time
  • Reviewers auditing whether a test strategy catches regressions before release

Skip it if

  • Teams with no web application or no interest in browser-based testing, since the guidance is specific to E2E tests
  • Anyone expecting the skill to write or run a full test suite automatically; it only lists the SKILL.md instructions and a reference file, and no scripts are included
  • Projects needing formal compliance certification, because the output is an informal review that may miss gaps

Try asking

  • “Review this project's CI config and tell me whether our checkout and login flows are covered by E2E tests that block merges”
  • “Suggest a Playwright setup for our authentication and form submission journeys”
  • “Explain E2E testing best practices for our team, including selectors and CI artifact uploads”
  • “Flag exact gaps where our E2E tests are documented but not automatically verified”
Step-by-step guide: how to use End-to-End Testing ReviewerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    e2e-testing.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip e2e-testing.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip e2e-testing.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Point the agent at a specific repository and CI configuration file so it can check enforcement, not just documentation.
  • Name the critical journeys in your product so the review targets your real risks rather than generic examples.
  • Read references/rule.md for framework-specific detail, and verify any suggested Playwright or Cypress code against current library docs before committing.

What's inside

  • references/rule.md
  • SKILL.md

Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.