Orchestrate dependent Git branches and pull requests in a stack order.
npx skills add https://github.com/erichugy/agentic.skills --skill stacked-prs-erichugy
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
Speed up reviews and reduce risk by breaking a feature into smaller, dependent pull requests instead of one large change.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
rarestgMerge dependent GitHub Pull Requests sequentially into the main branch.
arbazkhan971Finalize feature branches via merge, pull request, keep, or discard after build, lint, and tests.
EmasoftDetect languages in PRs and apply language-specific linters with consolidated findings.
elijahmurrayCheck out pull request branches, review code changes, and apply feedback.
