skills.rest
Joaovsales
JoaovsalesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-e2e

Execute real-browser end-to-end validation of user-facing criteria via MCP tool calls.

1|Updated Jan 27, 2026
Search Tags:#automation#testing#e2e#qa#browser#workflows
One-click install
npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill verify-e2e-joaovsales
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-e2e
Source: https://github.com/Joaovsales/coding-agent-workflow/tree/main/.claude/skills/verify-e2e
Command: npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill verify-e2e-joaovsales

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures real-browser end-to-end validation of user-facing criteria before wrap-up, preventing the release of features with unverified UI flows.

Core Features & Use Cases

  • End-to-end walkthroughs executed in a real browser via MCP tool calls to verify user journeys.
  • Automatic evidence logging to tasks/e2e-log.md and gating outcomes for wrap-up-session.
  • Pre-flight checks and guardrails: ensure specs, dev server health, and authenticated browser state before tests.
  • Integration with /build and /wrap-up-session gating to halt progression on failure.

Quick Start

Start the E2E gate by running a browser-based walkthrough and append results to tasks/e2e-log.md.

Frequently Asked Questions about verify-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end validation for UI workflows before release?▼

End-to-end validation executes real-browser walkthroughs of user-facing criteria to verify UI flows. It runs via MCP tool calls during builds or wrap-up gating to prevent releasing unverified features.

What do I need to run real-browser e2e tests during my build process?▼

Real-browser e2e tests require an active spec in specs/, a running dev server, and a valid authenticated browser session. Pre-flight checks ensure these prerequisites are met before validation begins.

Can I gate my wrap-up session to halt progression if UI navigation fails?▼

Wrap-up session gating halts progression on UI navigation failures. The skill integrates with build and wrap-up workflows to block releases when end-to-end validation detects broken user journeys.

How does end-to-end testing log validation evidence for QA review?▼

End-to-end testing logs validation evidence by appending walkthrough results to tasks/e2e-log.md. This automatic logging provides a persistent record of QA gating outcomes for review.

Why does my browser-based e2e walkthrough fail to validate UI state?▼

Browser-based e2e walkthroughs fail when pre-flight guardrails detect missing prerequisites. You must ensure the specs/ directory is populated, the dev server is healthy, and the browser session is authenticated.

What is the best way to prevent QA gaps in user-facing features?▼

Preventing QA gaps requires executing real-browser end-to-end validation of user-facing criteria before wrap-up. This applies during builds to verify UI state and navigation through actual user journeys.

Related Skills

Explore More Software Engineering Skills→
wasp-langwasp-lang
12

start-dev-server

Start the Wasp dev server with logs and browser console visibility.

Official
Advanced
Wilder1222Wilder1222
2

workflow

Orchestrate six-stage sprint workflows with artifact gates and inter-skill data flow.

Community
Advanced
AminAlamAminAlam
26

Automated Testing in CI/CD

Automate test execution and gating in CI/CD pipelines for medical devices.

Community
Intermediate
Svenja-devSvenja-dev
38

e2e-testing

Automate end-to-end browser testing for web applications with Playwright MCP.

Community
Intermediate