skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cut-epic

Create a long-lived feature branch from origin/develop and pin claude.flowkit.prBase to it.

Updated Apr 17, 2026
Search Tags:#git#workflow#feature-branch#flowkit#swarmkit#pr-base#cut-epic
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill cut-epic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cut-epic
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/cut-epic
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill cut-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a long-lived feature branch for a multi-PR epic, push it to origin, and scope claude.flowkit.prBase to it so every subsequent PR targets it. The epic branch lives until the epic ships. When it's ready, open a single PR from the epic branch to develop, then tear down the scope to revert PR targeting.

Core Features & Use Cases

  • Create a feature/<slug>-<issue> branch from origin/develop and push it to origin.
  • Pin claude.flowkit.prBase to the epic branch so subsequent PRs automatically target it.
  • Teardown and clear the scope when the epic ships to restore default PR targeting to develop.
  • Works with flowkit open-pr and pr, and swarm agents operating within the epic workflow.

Quick Start

Create and push the epic feature branch from origin/develop and scope claude.flowkit.prBase to it.

Frequently Asked Questions about cut-epic

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

FAQPage Schema
How do I create a long-lived feature branch for a multi-PR epic in git?▼

To create an epic branch for a multi-PR workflow, cut a feature branch from origin/develop and push it to origin. This isolates epic work across multiple PRs until the epic ships and merges back into develop.

What is the best way to manage PR targeting for a multi-PR epic workflow?▼

Pin claude.flowkit.prBase to the epic branch so subsequent PRs automatically target it. This scope management ensures every PR opened during the epic workflow targets the epic base instead of develop.

How do I restore default PR targeting to develop after an epic ships?▼

Tear down and clear the pr-base-scope when the epic ships to restore default PR targeting to develop. You then open a single PR from the epic branch to develop to merge the completed epic work.

Does cut-epic work with flowkit and swarmkit workflows?▼

Yes, cut-epic works with flowkit open-pr and pr actions, as well as swarm agents operating within the epic workflow. It scopes all flowkit and swarmkit actions to target the epic base branch.

What steps are required to set up an epic feature branch from origin/develop?▼

Setting up an epic branch requires explicit branch validation, remote fetch from origin/develop, creation and pushing of the feature branch, and scope management via pr-base-scope to target all actions to the epic base.

When should I avoid using a long-lived epic branch for feature work?▼

Avoid using a long-lived epic branch for single-PR tasks or work that does not require isolation across multiple PRs. Epic branches are designed for multi-PR workflows that need to isolate epic work until it ships.

Related Skills

Explore More Software Engineering Skills→
smallorbitsmallorbit

create-branch

Create and checkout Git branches from origin/develop.

Community
Intermediate
xiduzoxiduzo
7

wtf.create-pr

Generate pull request titles and descriptions from branch names and spec hierarchies.

Community
Advanced
smallorbitsmallorbit

preview-epic-direct

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

Community
Advanced
izyanrajwaniizyanrajwani
4

finishing-a-development-branch

Automate Git branch completion with tests, base-branch selection, and merge or PR actions.

Community
Advanced