stack-branch

Create a new branch from an existing PR with Jira-based naming.

6|Updated Jan 22, 2026

Search Tags:#git #workflow #devops #branching #jira #pull-request #stack-branch

Ready to run

npx skills add https://github.com/flurdy/agent-skills --skill stack-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stack-branch
Source: https://github.com/flurdy/agent-skills/tree/main/skills/stack-branch
Command: npx skills add https://github.com/flurdy/agent-skills --skill stack-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple tasks depend on a parent PR, this Skill lets you create a new branch derived from that PR (not main) so you can start work immediately without waiting for the parent to merge.

Core Features & Use Cases

Create a new branch based on an existing PR branch (not main) for dependent work.
Map a Jira ticket to a conventional branch name to maintain traceability.
Use when implementing changes that must align with a parent PR.

Quick Start

Create a new stack branch from the parent PR by providing the Jira ticket and an optional parent branch.

Frequently Asked Questions about stack-branch

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

FAQPage Schema

How do I create a git branch based on an unmerged pull request?▼

To create a git branch based on an unmerged pull request, you can derive a new stack branch from the existing PR branch. This allows you to start dependent work immediately without waiting for the parent PR to merge into main.

How do I map a Jira ticket to a conventional git branch name?▼

To map a Jira ticket to a conventional git branch name, the stack-branch process formats the branch name by mapping Jira ticket types to specific prefixes. This maintains traceability between your feature branches and the originating Jira tickets.

When should I use stacked branches instead of branching directly from main?▼

You should use stacked branches instead of branching from main when multiple tasks depend on a parent PR. This lets you start dependent work immediately and ensures your changes align with the parent PR before it merges.

Can I automatically detect the parent branch when creating a dependent PR branch?▼

Yes, you can automatically detect the parent branch when creating a dependent PR branch. The process supports optional parent-branch specification or can automatically detect the parent from your current feature branch.

How do I push a new dependent feature branch to origin for review?▼

To push a new dependent feature branch to origin for review, the stack creation process pushes the newly formatted branch directly to origin. This makes the dependent PR branch available for review immediately after creation.