stacking-pull-requests SKILL.md skillA
stacking-pull-requests from kamiazya/whiteboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamiazya/whiteboard/stacking-pull-requests@git:20261016.bbfc32dPins git:20261016.bbfc32d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamiazya/whiteboard
- Path
.claude/skills/stacking-pull-requests/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261016.bbfc32d, committed Oct 16, 2026
- First version recorded
- Aug 11, 2026
- Size
- 7,559 bytes
- Repository stars
- 10
- License
- Apache-2.0
Operates a stack of dependent pull requests in the whiteboard repo with the gh-stack extension — creating a stack across architecture layers, keeping it rebased as main moves, and landing it. Use when a change spans several layers that must merge in order (a shared package under an MCP tool under a web surface), when the user says stacked PR / stack / 積む / スタック, or when a branch's base is another feature branch rather than main. For deciding WHETHER to stack, see the mode table in…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Stacking pull requests `gh stack` (GitHub's stacked pull requests, public preview since 2026-07-30) turns a chain of dependent branches into one reviewable stack: each PR shows only its own layer's diff, reviewers work in parallel, and merging is atomic up to whichever PR you pick. **Whether to stack at all is a `dev-flow.md` decision, not this skill's.** This skill is the operating procedure once the answer is yes. ## Prerequisite ```bash gh extension install github/gh-stack ``` One-time per machine. `gh stack --help` lists every subcommand; the ones below are the whole day-to-day surface. ## Stack order is not a choice here This repo's dependency direction is already fixed by `.claude/rules/architecture-map.md`, and a stack must follow it — a lower layer cannot depend on a higher one. Order the layers by that table's dependency EDGES (each row's "Checked dependencies" column, which `tools/arch-lint` holds to the manifests), not by its row order: the rows are not topological — `canvas-render` is listed above `plugin-visual`, which it depends on, so `plugin-visual` goes lower in the stack. A copy of the order here is what goes stale. …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/stacking-pull-requests@sha256:8d895b29f6960887The line at the top of this page pins the label git:20261016.bbfc32d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2qvbxwieg2tmgk7u)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 11, 2026 and Oct 16, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.bbfc32d latest | 2026-10-16 | bbfc32d | 7,559 B | A | view · diff |
| git:20261005.3fd603d | 2026-10-05 | 3fd603d | 7,321 B | A | view · diff |
| git:20260816.3a33d1a | 2026-08-16 | 3a33d1a | 7,183 B | A | view · diff |
| git:20260813.1037ab6 | 2026-08-13 | 1037ab6 | 7,218 B | A | view · diff |
| git:20260811.c1e79d2 | 2026-08-11 | c1e79d2 | 6,675 B | A | view · diff |
| git:20260811.7b616bf | 2026-08-11 | 7b616bf | 6,178 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7559 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kamiazya/whiteboard · 10 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2qvbxwieg2tmgk7u GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/stacking-pull-requests GET https://markdownregistry.com/api/v1/blob/8d895b29f69608872e50b4b384a2628f232374ac4531c06294ed736b729d892f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.