t-demo-run

Run a single demo E2E test, diagnose failures, and dispatch fixes until it passes.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-demo-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-demo-run
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-demo-run
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-demo-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end demo validation process by running a single demo E2E test, diagnosing failures, and orchestrating fixes across agents until the test passes.

Core Features & Use Cases

  • Orchestrate a full-demo workflow: execute a demo test file, identify failures, and dispatch structured diagnostics to appropriate agents for targeted fixes.
  • Support iterative repair cycles: loop through diagnosis, development, and retesting until success, with automated status reporting.
  • Output machine-readable results: final run status, logs path, and run identifiers to enable traceability and automation.

Quick Start

Invoke t-demo-run with a demo file path to start the end-to-end run and automatic repair cycle.

Frequently Asked Questions about t-demo-run

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

FAQPage Schema
How do I automate end-to-end test diagnosis and fix failures across backend and frontend layers?

Automated end-to-end test diagnosis executes a demo test file, identifies failures, and dispatches structured diagnostics to appropriate agents for targeted fixes across backend, frontend, and automation layers until the test passes.

What is the best way to run an iterative E2E smoke check and automatically repair failing test cycles?

Iterative E2E smoke checks run a demo test, diagnose failures, and orchestrate automated repair cycles by dispatching fixes to agents, retesting continuously until success, and outputting machine-readable final run statuses and logs.

Does agent-dispatch test automation work for validating feature demos without manual intervention?

Agent-dispatch test automation supports PRD-like demos and feature validations by executing a single end-to-end test, orchestrating structured fixes across agents, and re-running iteratively until the test passes with automated status reporting.

How to get machine-readable results and run identifiers from a single demo end-to-end test?

To get machine-readable results from a demo end-to-end test, invoke the run with a demo file path; the process outputs final run status, logs path, and run identifiers to enable full traceability and downstream automation.

What are the limitations of using a single demo E2E test for feature validation and smoke checks?

Using a single demo E2E test limits validation scope to one test file per run, enforcing a structured cycle of diagnosis, development, and retesting, which may not cover comprehensive multi-file test suite scenarios.