test-flow

Orchestrate automatic unit and E2E test generation and execution flows for Builder.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill test-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-flow
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/test-flow
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill test-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically orchestrates test generation and execution flows for Builder based on code changes, reducing manual toil and aligning tests with new work.

Core Features & Use Cases

  • Automatic Activity Resolution determines which tests to run from changed files and code patterns.
  • Deterministic test pipeline collects changes, resolves activities, and executes baseline checks, unit tests, critics, and E2E decisions without prompts.
  • Use Case: Apply this when you modify code to ensure appropriate tests run and E2E can be deferred or executed based on project needs.

Quick Start

Tell Builder to auto-generate and run tests for the changed files.

Frequently Asked Questions about test-flow

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

FAQPage Schema
How do I automate unit and E2E test generation from code changes?

Automating test generation from code changes is handled by orchestrating a deterministic pipeline that resolves activities from modified files and generates matching unit and E2E tests. The pipeline collects changes, runs baseline checks, and executes tests without manual prompts.

What is automatic activity resolution for test execution flows?

Automatic activity resolution determines which tests to run by analyzing changed files and code patterns. It maps file modifications to relevant test activities, ensuring the test pipeline executes only the appropriate unit tests, critics, and E2E decisions for the specific changes made.

Can I defer E2E tests based on project needs during automated test flows?

Deferring E2E tests during automated test flows is supported through context-aware decision-making. The pipeline evaluates project needs and applies deferral logic when appropriate, allowing you to skip or postpone end-to-end execution while still running baseline checks and unit tests.

How do I run a deterministic test pipeline without manual prompts?

Running a deterministic test pipeline without prompts requires a tool that collects changes, resolves activities, and executes baseline checks, unit tests, critics, and E2E decisions automatically. This ensures consistent execution steps driven by code modifications rather than manual intervention.

What are the limitations of automating test generation for code changes?

Limitations of automating test generation include dependency on accurate code pattern recognition for activity resolution and the need for project context to make correct E2E deferral decisions. If changed files lack clear patterns or context, the pipeline may generate inappropriate tests or defer E2E incorrectly.