preview-epic-stacked

Create a local preview branch to merge and validate interdependent open PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesize and validate the integrated state of an epic whose contributions are open PRs by creating a throwaway local preview branch, enabling safe verification without pushing.

Core Features & Use Cases

  • Discover and order the PR stack from root to leaf based on base/head relationships.
  • Attempt octopus merge for a full integration, with a sequential fallback on conflicts, reporting the conflicted PR.
  • Generate a local preview branch name, fetch necessary refs, and prepare for verification steps defined in .squadkit/config.json.

Quick Start

Run the flowkit:preview-epic command with --base <branch> --epic <branch> to initialize a local preview workflow.

Frequently Asked Questions about preview-epic-stacked

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

FAQPage Schema
How do I preview stacked PRs locally before merging an epic?

To preview stacked PRs locally, create a throwaway local preview branch that synthesizes the integrated state of open PRs, enabling safe verification of an epic flow without pushing. It discovers the PR stack from root to leaf and attempts an octopus merge with a sequential fallback on conflicts.

What is a stacked PR workflow for epic branches?

A stacked PR workflow for epic branches involves an epic spanning multiple interdependent PRs across a base branch. This approach discovers and orders the PR stack from root to leaf based on base/head relationships to validate the integrated state before merging to the mainline.

How do I resolve merge conflicts when previewing an epic locally?

To resolve merge conflicts when previewing an epic locally, the process attempts an octopus merge for full integration and falls back to sequential merges on conflicts. It reports the specific conflicted PR, allowing you to address integration issues before pushing.

Can I configure verification steps for a local preview branch?

Yes, you can configure verification steps for a local preview branch using the .squadkit/config.json file. This configuration allows you to define specific validation checks to run after the preview branch is created and the PR stack is merged.

Do I need any external dependencies to run a local preview of an epic stack?

No external dependencies are required to run a local preview of an epic stack. The process relies on standard git merge mechanisms, dispatcher argument parsing, and local configuration via .squadkit/config.json to fetch refs and prepare the throwaway branch.

What's the best way to verify multiple interdependent open PRs before merging?

The best way to verify multiple interdependent open PRs before merging is to generate a throwaway local preview branch that fetches necessary refs and applies an octopus merge. This enables safe verification of the integrated epic state without pushing to the mainline.