stacked-prlisted

# Stacked PRs Use GitHub's `gh stack` extension. It already does parent tracking, cascading rebase, PR base retargeting, and bottom-up merging. Do **not** hand-roll this with `git rebase --update-refs`, `git config branch.*.parent`, or manual `gh pr create --base` — that reimplements the extension badly and drifts from what GitHub's UI shows. Public preview — flags may change. `gh stack <cmd> --help` is authoritative over this file. ## First: does this actually need to be a stack? Stacking couples the PRs. They merge bottom-up only, so a review stall or a revert on a lower layer blocks everything above it. Before running any command here, check whether the changes actually depend on each other — later layers building on earlier layers' code, or a split of one logical change too big to review at once. If they're independent (unrelated files, either could merge first, no shared new symbols), **stop and ask the user whether they really want a stack**, and say why you're asking: independent PRs opened straight against the trunk merge in any order and don't block each other. Only proceed once they confirm. ## Setup (once) ```bash gh extension install github/gh-stack gh stack alias # optional: shorter command ``` If the repo's trunk is not the default branch, every `init` must say so, or the bottom PR targets the wrong branch: ```bash gh stack init --base develop <bottom-branch> ``` ## Create a stack ```bash gh stack init feat-auth # add --base <trunk> if