e2e-flow

Generate and verify end-to-end test flows from plans, mappings, PR diffs, or CLI intents.

3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iamcxa/kc-claude-plugins --skill e2e-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-flow
Source: https://github.com/iamcxa/kc-claude-plugins/tree/main/e2e-pipeline/skills/e2e-flow
Command: npx skills add https://github.com/iamcxa/kc-claude-plugins --skill e2e-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and verify end-to-end test flows from plans, mappings, PR diffs, or CLI-only intents to reduce manual test authoring, brittle selectors, and verification overhead across browser and backend domains.

Core Features & Use Cases

  • Flow generation from multiple sources: Create structured flow YAML from conversation context, plan files, or PR diffs.
  • Dual-mode verification: Verify browser flows with auto-repair and CLI/API flows via Execute external/Verify external steps and asciinema recordings.
  • CI & PR integration: Commit verified flows to PRs, upload media assets to draft releases, and produce detailed reports with corrections and trace analysis.
  • Resilience and safety: Mapping discovery, sentinel-based write authorization, Teams/subagent fallbacks, pre-flight checks, and trace-analyzer post-processing to handle failures and crashes.

Quick Start

Run the e2e-flow skill to generate and verify a flow from the current context by invoking /e2e-flow --mapping projects --verify-only.

Frequently Asked Questions about e2e-flow

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

FAQPage Schema
How do I generate E2E test flows from a pull request diff?

You can generate E2E test flows from PR diffs by running the e2e-flow skill, which analyzes the diff to create structured flow YAML. It also supports generating flows from conversation context, plan files, or CLI intents.

How do I verify CLI and API test flows with backend recordings?

To verify CLI and API test flows, the e2e-flow skill uses Execute external and Verify external steps for backend verification. It captures asciinema recordings to validate CLI/API interactions and handle trace analysis.

What is browser automation auto-repair for E2E testing?

Browser automation auto-repair is a verification mechanism that fixes brittle selectors during E2E test flows. The e2e-flow skill applies mapping discovery and trace analysis to automatically correct failing browser UI flows.

Can I commit verified test flows directly to a pull request?

Yes, you can commit verified test flows directly to pull requests using the e2e-flow skill. It integrates into CI pipelines to upload media assets to draft releases and produce detailed correction reports.

Does e2e-flow work without external dependencies?

Yes, e2e-flow works without external dependencies, using internal sentinel-based write authorization and subagent fallbacks. It handles mapping discovery and pre-flight checks natively to ensure resilience.

Why do my browser UI test flows fail during verification?

Browser UI test flows often fail due to brittle selectors or mapping discovery issues. The e2e-flow skill addresses this by applying auto-repair, sentinel-based write authorization, and trace-analyzer post-processing to handle crashes.