skills.rest
bobmatnyc
bobmatnycCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stacked-prs

Create and coordinate stacked pull requests with sequential branch basing.

3|1|Updated Dec 8, 2025
Search Tags:#dependencies#branching#code-review#pull-requests#git-workflow#version-control#stacked-prs
One-click install
npx skills add https://github.com/bobmatnyc/terminator --skill stacked-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacked-prs
Source: https://github.com/bobmatnyc/terminator/tree/main/.claude/skills/universal-collaboration-stacked-prs
Command: npx skills add https://github.com/bobmatnyc/terminator --skill stacked-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacked PRs help teams manage complex feature development by splitting changes into dependent PRs that build on previous work, enabling staged reviews and safer merges.

Core Features & Use Cases

  • Dependent PRs with clear base on previous branch: Ensure reviews follow the dependency chain.
  • Sequential branching and standardized PRs: Keep naming and base relationships consistent for easy auditing.
  • Use Case: For example, implement a base authentication feature, then add a user profile PR that builds on the base, followed by an admin panel PR.

Quick Start

Start from main and create an initial base PR, then create dependent PRs that branch off the immediate predecessor's branch, ensuring the base is the previous feature branch, not main.

Frequently Asked Questions about stacked-prs

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

FAQPage Schema
How do I manage stacked pull requests for a complex feature with multiple dependencies?▼

Stacked pull requests split complex feature development into dependent PRs that build on previous branches, enabling staged reviews and safer merges. Each dependent PR branches off its immediate predecessor rather than the main branch.

What is the correct git workflow for sequential branching in stacked PRs?▼

Sequential branching in stacked PRs requires creating an initial base PR from main, then branching dependent PRs off the immediate predecessor's feature branch. This enforces sequential basing and maintains correct dependency chains.

When do I need stacked PRs instead of a single pull request?▼

Stacked PRs are needed for software projects requiring phased delivery and dependency tracking across multiple changes. They coordinate complex feature development by splitting work into dependent PRs for controlled integration and staged code review.

How do I keep PR descriptions consistent across a stacked pull request chain?▼

Standardized PR descriptions in stacked PRs keep naming and base relationships consistent for easy auditing. This ensures reviews follow the dependency chain correctly and maintains clear base references across all branches.

Does a stacked PR workflow require rebasing when the base branch changes?▼

A stacked PR workflow uses rebase-guided workflows to ensure correct dependency chains. When a base branch changes, dependent PRs must be rebased onto the updated predecessor to maintain the sequential branch structure.

Can I use stacked PRs for adding features that depend on unmerged branches?▼

Yes, stacked PRs handle dependent features by basing new work on unmerged predecessor branches. For example, a user profile PR can build on an unmerged authentication base PR, followed by an admin panel PR building on the profile branch.

Related Skills

Explore More Software Engineering Skills→
bluejayAbluejayA
2

aidlc-using-git-worktrees

Create an isolated git worktree before code generation begins.

Community
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
zMynxxzMynxx

chained-pr

Split oversized pull requests into focused reviewable PR chains.

Community
Advanced