stacked-prs

Orchestrate dependent Git branches and pull requests in a stack order.

Updated Apr 10, 2026

Search Tags:#git #workflow #branching #code-review #pull-request #stacked-prs

Ready to run

npx skills add https://github.com/erichugy/agentic.skills --skill stacked-prs-erichugy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stacked-prs
Source: https://github.com/erichugy/agentic.skills/tree/main/stacked-prs
Command: npx skills add https://github.com/erichugy/agentic.skills --skill stacked-prs-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speed up reviews and reduce risk by breaking a feature into smaller, dependent pull requests instead of one large change.

Core Features & Use Cases

Stack PRs by creating sequential branches from the previous one and targeting non-main bases.
Each PR focuses on a single concern for easier reviews.
Merge from the bottom of the stack to ensure proper dependency flow.

Quick Start

Define the stack, create the first branch from main, then create each next branch from the previous branch and label PRs as part of the stack.

Frequently Asked Questions about stacked-prs

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

FAQPage Schema

What is stacked pull requests workflow in Git?▼

Stacked pull requests split a feature into sequential, dependent Git branches where each PR targets the previous branch instead of main. This approach breaks large changes into smaller, reviewable units to speed up code review and reduce merge risk.

How do I create stacked PRs for dependent Git branches?▼

To create stacked PRs, define the stack order, create the first branch from main, then create each subsequent branch from the previous one. Label each PR to indicate its position in the stack and target the preceding branch as the base.

When should I use stacked PRs instead of a single large pull request?▼

Use stacked PRs when a feature can be split into sequential, interdependent changes. This enforces per-PR scoping for single concerns, ensuring deterministic review and merge order while keeping each change focused and manageable.

How do I merge stacked pull requests safely?▼

Merge stacked pull requests from the bottom of the stack upward to ensure proper dependency flow. This bottom-to-top approach maintains stable base branches and prevents conflicts from merging higher-level dependent branches before their prerequisites.

Can I target non-main branches as bases for stacked PRs?▼

Yes, stacked PRs work by targeting non-main base branches. Each branch in the stack uses the previous branch as its base, establishing clear base-relational branching that keeps dependent changes isolated until merge.

Does stacked PRs workflow require specific Git tools or dependencies?▼

No specific Git tools or dependencies are required. The workflow orchestrates dependent Git branches and PRs using standard branching and labeling practices, relying on sequential branch creation and per-PR scoping for deterministic review.