Stacked PR Management

Create dependent PR chains with base/child relationships using GitHub CLI.

5|3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/constellos/claude-code-plugins --skill stacked-pr-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Stacked PR Management
Source: https://github.com/constellos/claude-code-plugins/tree/main/plugins/github-orchestration/skills/stacked-pr-management
Command: npx skills add https://github.com/constellos/claude-code-plugins --skill stacked-pr-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacked PR Management solves the coordination challenge of large features split into multiple dependent pull requests by enabling end-to-end PR chains with clear base/child relationships and review order.

Core Features & Use Cases

  • Create PR chains: establish a sequence where each PR bases on the previous.
  • Visualize and track stacks: quickly see the dependency structure and merge order.
  • Rebase and merge in order: automatically rebase dependents when base PR is updated and merge bottom-up.
  • Use Case: when shipping a large feature across multiple reviews, developers work on isolated PRs while preserving the overall integration flow.

Quick Start

To build a 3-PR stack, create the base branch and subsequent feature branches, push them, then create PRs with explicit base relationships using the GitHub CLI commands shown in the examples. If needed, initialize a stack store with the provided utilities.

Frequently Asked Questions about Stacked PR Management

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

FAQPage Schema
How do I manage stacked pull requests on GitHub for a large feature split across multiple reviews?

Stacked pull requests link dependent GitHub PRs into a chain where each builds on the previous. This manages large features across multiple reviews by preserving base and child relationships, tracking merge order, and visualizing the dependency structure.

How do I rebase dependent pull requests when the base PR in a stack is updated?

Rebasing dependent pull requests in a stack happens automatically when the base PR is updated. The stack management workflow updates child branches to reflect changes in their parent PRs, ensuring the chain remains consistent before executing the bottom-up merge order.

What is the merge order for stacked PRs and how does PR visualization help?

The merge order for stacked PRs is bottom-up, starting from the base PR and moving sequentially through dependents. PR visualization helps by quickly displaying the dependency structure and merge sequence, clarifying which pull requests to review and integrate first.

Can I use the GitHub CLI to create dependent PR chains with explicit base relationships?

Yes, you can use the GitHub CLI to create dependent PR chains by pushing feature branches and creating pull requests with explicit base relationships. Shell scripts and metadata-based activation manage these stack operations, allowing you to initialize a stack store for tracking.

When do I need to split a large feature into dependent pull requests?

You need to split a large feature into dependent pull requests when shipping across multiple review iterations. This workflow allows developers to work on isolated PRs while preserving the overall integration flow, solving the coordination challenge of managing base and child relationships.