e2e

Convert product changes into end-to-end tests with pass, fail, or skip reports.

88|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/heliohq/ship --skill e2e-heliohq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/heliohq/ship/tree/main/skills/e2e
Command: npx skills add https://github.com/heliohq/ship --skill e2e-heliohq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns product changes into durable end-to-end tests so teams can prove behavior against a real app instead of relying on code review alone. It reduces flaky confidence by making acceptance criteria executable, repeatable, and committed to the repository.

Core Features & Use Cases

  • Framework detection: Finds the existing E2E stack or scaffolds a sensible default when none exists.
  • Acceptance coverage: Converts specs and diffs into user-visible tests for web, API, and workflow changes.
  • Run and evidence handling: Starts the app, executes tests, captures failures, and records artifacts and reports.
  • Use cases: Great for regression tests after feature work, browser-flow validation, and quality gates before review.

Quick Start

Use the e2e skill to inspect the change, write or update the right end-to-end tests, run them against the real app, and report the results.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I convert product changes into end-to-end tests automatically?

To convert product changes into end-to-end tests, this Skill inspects your specs and diffs to generate user-visible assertions for web, API, and workflow changes, ensuring acceptance criteria are executable and repeatable.

Does this tool scaffold a default E2E testing framework if one is missing?

Yes, framework detection automatically identifies your existing E2E stack and scaffolds a sensible default when none exists, allowing you to generate regression tests and browser-flow validations without manual setup.

How do I capture test artifacts and evidence during end-to-end testing?

During end-to-end testing, the tool coordinates app startup and cleanup, executes tests, captures failure artifacts, and records structured pass, fail, or skip reports to provide durable verification evidence.

What is the best way to create regression sentinels after feature work?

The best way to create regression sentinels is converting feature diffs into committed end-to-end tests with user-visible assertions, running them against a real app to prove behavior before quality gates and code review.

Why do I need app startup and cleanup coordination for acceptance tests?

App startup and cleanup coordination is required for acceptance tests to guarantee a stable, real application environment, which reduces flaky confidence and ensures structured pass, fail, or skip reporting is accurately captured.

Can I use this for API and workflow changes or is it limited to browser flows?

You can use this for API and workflow changes alongside browser flows, as it applies acceptance coverage across web, API, and workflow modifications to establish comprehensive regression sentinels and executable specs.