What problem does it solve? When several pieces of work depend on each other, opening all PRs against the main branch creates quadratic merge conflicts, stale branches, and silently lost work. This Skill defines a disciplined pattern for stacking PRs so dependent changes merge cleanly in order. ## Core Features & Use Cases - Chained branching: Branch each dependent work item from the previous branch instead of the epic branch, and set each PR's base to its predecessor. - Ordered bottom-up merging: Retarget the heir PR's base after each merge, close linked issues manually since the host only auto-closes on merges to the default branch, and record merge order in PR bodies. - Conflict and lag detection: Query mergeable status across all open PRs with the GitHub CLI, merge main only on actual conflicts, and detect silently lagging local branch stacks. - Use Case: You finished five sequential tasks in one session on one epic. Use this pattern to chain the branches, open stacked PRs with declared merge order, run a trial merge to find collisions, and hand the owner a clean bottom-up merge list. ## Quick Start Ask the AI to organize my pending feature branches into a stacked PR chain with the correct base branches and merge order using the git-workflow-stack pattern.
