How do I install the Stacked Pr skill?

Run npx skillmds@latest add luisurrutia/stacked-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Stacked Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stacked Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stacked Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Stacked Pr?

LuisUrrutia (@luisurrutia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stacked Pr by luisurrutia — Agent Skill

Name: Stacked Pr
Author: LuisUrrutia

Stacked Pr

Manage GitHub stacked pull requests and dependent PR chains. Use for designing or operating a stack, splitting work into reviewable layers, recovering divergent stacks, or changing CI workflows, bots, or webhook integrations whose behavior depends on stack state.

LuisUrrutia fb1c0de 16 files · 33.1 KB Updated Sep 17, 2026

File contents

Stacked pull requests

A stack is a linear chain of pull requests in one repository. The bottom targets the trunk; every layer above targets the branch below it, so each PR shows only its own concern.

main <- data-model <- api-routes <- ui
          bottom                  top

Dependencies point toward the trunk, changes to a lower layer cascade upward, and merges proceed bottom-up.

Scope and safety

Bound the work to the requested operation. Explanations, reviews, and status checks are read-only. Creation and maintenance may change only the local branches and linked PRs needed for that operation. A later lifecycle stage must be explicitly included in the request.

Merging requires the user's explicit approval for the exact PR set and merge method immediately before the merge command. Preserve unrelated dirty-tree work. Before rewriting ancestry, record the current branch and relevant tips so every original commit remains reachable until verification.

Route the request

Choose one primary route. Load its file, select the requested operation there, and stop when that operation's completion criterion is satisfied. For a request that explicitly includes several operations, complete them in dependency order and satisfy each criterion before loading the next:

CLI — local development, navigation, submit, sync, or cascading rebases owned by github/gh-stack. Load references/cli-workflow.md.
API — perform a concrete native-stack operation through REST, whether interactive or automated. Load references/api-workflow.md.
Manual — GitHub reports native stacks unavailable, or the user wants ordinary dependent PRs. Load references/manual-chain.md.
Stack-aware CI and integrations — load references/automation.md when the fix changes a workflow, bot, GraphQL client, or webhook because of stack state. Product-code and test failures use CLI, API, or manual.

Keep one mutation owner throughout an operation. Read-only inspection through another interface is safe; switching writers during a mutation can desynchronize local tracking and GitHub state.

Routing is complete when the requested operation and primary route are identified. For repository-bound work, also identify the repository, trunk, push remote, and authenticated principal; for a mutation, record the current branch, dirty paths, relevant branch tips, and intended remote objects before changing state.

Conditional references

The primary route points to these only when their branch is reached:

references/stack-design.md — plan layers before creating branches or splitting existing work.
references/troubleshooting.md — recover from a failure, divergence, adoption, restructuring, worktrees, or another branch manager.

---name: stacked-prdescription: Manage GitHub stacked pull requests and dependent PR chains. Use for designing or operating a stack, splitting work into reviewable layers, recovering divergent stacks, or changing CI workflows, bots, or webhook integrations whose behavior depends on stack state.---# Stacked pull requestsA **stack** is a linear chain of pull requests in one repository. The **bottom** targets the**trunk**; every layer above targets the branch below it, so each PR shows only its own concern.```textmain <- data-model <- api-routes <- ui bottom top```Dependencies point toward the trunk, changes to a lower layer cascade upward, and merges proceedbottom-up.## Scope and safetyBound the work to the requested operation. Explanations, reviews, and status checks are read-only.Creation and maintenance may change only the local branches and linked PRs needed for thatoperation. A later lifecycle stage must be explicitly included in the request.Merging requires the user's explicit approval for the exact PR set and merge method immediatelybefore the merge command. Preserve unrelated dirty-tree work. Before rewriting ancestry, record thecurrent branch and relevant tips so every original commit remains reachable until verification.## Route the requestChoose one primary route. Load its file, select the requested operation there, and stop when thatoperation's completion criterion is satisfied. For a request that explicitly includes severaloperations, complete them in dependency order and satisfy each criterion before loading the next:- **CLI** — local development, navigation, submit, sync, or cascading rebases owned by `github/gh-stack`. Load [references/cli-workflow.md](references/cli-workflow.md).- **API** — perform a concrete native-stack operation through REST, whether interactive or automated. Load [references/api-workflow.md](references/api-workflow.md).- **Manual** — GitHub reports native stacks unavailable, or the user wants ordinary dependent PRs. Load [references/manual-chain.md](references/manual-chain.md).- **Stack-aware CI and integrations** — load [references/automation.md](references/automation.md) when the fix changes a workflow, bot, GraphQL client, or webhook because of stack state. Product-code and test failures use CLI, API, or manual.Keep one mutation owner throughout an operation. Read-only inspection through another interface issafe; switching writers during a mutation can desynchronize local tracking and GitHub state.Routing is complete when the requested operation and primary route are identified. Forrepository-bound work, also identify the repository, trunk, push remote, and authenticatedprincipal; for a mutation, record the current branch, dirty paths, relevant branch tips, andintended remote objects before changing state.## Conditional referencesThe primary route points to these only when their branch is reached:- [references/stack-design.md](references/stack-design.md) — plan layers before creating branches or splitting existing work.- [references/troubleshooting.md](references/troubleshooting.md) — recover from a failure, divergence, adoption, restructuring, worktrees, or another branch manager.

Frequently asked questions