preview-epic-direct

Fast-forward an epic branch and execute verification commands from config.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill preview-epic-direct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-epic-direct
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/preview-epic-direct
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill preview-epic-direct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview-epic sub-skill for the direct-merge-to-epic (Model B) flow — fast-forward the long-lived feature branch locally and run verify directly against its HEAD (no synthesis needed). Invoked by flowkit:preview-epic after auto-detection; not meant to be called directly.

Core Features & Use Cases

  • Coordinates fast-forwarded verification of the epic branch by checking out the epic locally and executing verification on its HEAD.
  • Reads verification commands from the squadkit configuration and supports optional install/typecheck/test/lint steps, prompting for missing commands when needed.
  • Tracks and reports the merged PR composition and verification outcomes to guide downstream actions.

Quick Start

Invoke the dispatcher with the required --base and --epic arguments to fast-forward the epic locally and execute verification on its HEAD.

Frequently Asked Questions about preview-epic-direct

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

FAQPage Schema
How do I verify a long-lived epic branch after a fast-forward merge?

To verify a long-lived epic branch after a fast-forward merge, checkout the epic branch locally, parse base and epic arguments, fetch updates, and run verification commands directly against its HEAD.

What is the direct-merge-to-epic flow in branch management?

The direct-merge-to-epic flow is a branch management model where changes are merged directly into a long-lived epic branch, allowing local fast-forward updates and direct HEAD verification without synthesis.

How do I run install, typecheck, test, and lint commands on an epic branch?

Run install, typecheck, test, and lint commands by reading verification configurations from .squadkit/config.json. If commands are missing, the workflow prompts for them before executing and reporting outcomes.

Do I need a configuration file to automate epic branch verification?

Yes, you need a .squadkit/config.json file to automate epic branch verification. The workflow reads verification commands from this file, prompting for missing commands to ensure proper execution.

Can I call the direct epic verification workflow directly from the command line?

No, direct epic verification is not meant to be called directly. It is invoked by a dispatcher after auto-detection, requiring base and epic arguments to execute the fast-forward and verification process.