Stacked & Multi-base PRs
SkillDev toolsHandle dependent/stacked PRs and same-code-on-multiple-bases correctly. Use for a PR stacked on another, or when the same change must land on the default branch plus a release/production branch.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Stacked & Multi-base PRs skill
What this skill tells your AI
The instructions your AI receives, as published by outthislife/brooklyn-skills in skills/stacked-pr/SKILL.md and read by ahel’s review.
Stacked (dependent) PRs
A child PR builds on a parent PR's branch. Update the stack bottom-up:
- Update the parent branch/PR first.
- Rebase the child onto the updated parent — not onto the default branch, and never "merge main into the leaf" as the only step.
- Push each level; keep each PR's base pointing at the one below it.
Multi-base (release + default)
Some orgs require the same change on the default branch AND a release/production branch:
- Confirm the required target branches from the repo's rules.
- Land the change once, then cherry-pick/port the identical code to the other base as a second PR.
- Keep the two PRs' code identical; note the sibling in each description.
Don't
- Collapse a stack by merging the default branch into the child.
- Let the two base PRs drift apart.
- Finish without listing every PR/MR in the stack as a link.
Signals
- GitHub stars
- 192
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
stacked-pr- Source
- github.com/outthislife/brooklyn-skills