菜单
Create, adopt, extend, submit, sync, restructure, inspect, or merge dependent pull requests with the official gh-stack extension. Use when the user requests stacked PRs, a plan or task list declares PR layers, or work crosses a stack-layer boundary.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Integralist/agent-skills --skill stacked-prs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
MANDATORY for any work on Go files (*.go). Load this before editing, reviewing, or creating any *.go file. Go coding conventions and style guide covering naming, error handling, testing, HTTP handlers, caching, concurrency, and observability.
Rewrite text to be more concise, clear, and direct without losing critical information. Inventories load-bearing details first, rewrites, then audits the rewrite to verify nothing essential was dropped — for a plan, technical guide, agent instructions, or any prose too long or hard to follow.
Write or improve technical documentation. Applies documentation best practices: brevity, focusing on why and what rather than how, simple visualizations, modularization, and decoupling from volatile code. Use when writing new documentation from scratch, or editing, or reviewing and rewriting existing documents for clarity and quality.
基于 SOC 职业分类
正在显示 SKILL.md
| name | stacked-prs |
| description | Create, adopt, extend, submit, sync, restructure, inspect, or merge dependent pull requests with the official gh-stack extension. Use when the user requests stacked PRs, a plan or task list declares PR layers, or work crosses a stack-layer boundary. |
| allowed-tools | Bash(git branch:*), Bash(git status:*), Bash(gh extension:*), Bash(gh stack:*) |
Manage dependent pull requests with gh stack.
A stack layer is a confirmed review unit, not a task. One layer may contain several tasks or vertical slices.
Verify the extension.
gh stack --help
If unavailable, ask before installing it:
gh extension install github/gh-stack
Resolve the delivery mapping.
Use Pull Request Delivery from the active project plan or task document
when present. If neither declares delivery, determine and confirm the shape
using
PULL-REQUEST-DELIVERY.md.
If the confirmed mode is not Stack, stop and use the ordinary branch and
PR workflow for each review unit.
Create or adopt the stack.
For new work, initialize the bottom layer. Add higher layers only when work moves across their confirmed boundary:
gh stack init --base <trunk> <bottom-branch>
gh stack add <next-branch>
Adopt existing branches in bottom-to-top order:
gh stack init --base <trunk> <bottom> <middle> <top>
Check out an existing stack or layer with:
gh stack checkout <stack-number-or-branch>
Use gh stack link when PRs already exist on GitHub and local stack
tracking is unnecessary.
Work and submit.
Complete every task assigned to the current layer on its branch. Use the
commit skill for commits. Run gh stack add only
when entering the next layer.
Inspect and submit the complete stack:
gh stack view --short
gh stack submit
Prefer the interactive submit editor so the user can review every PR's
title, body, and draft state. Use --auto only when the user accepts
generated titles; it creates new PRs as drafts unless --open is set.
Keep the stack current with gh stack sync. Use gh stack rebase to
resolve rebase conflicts and gh stack modify to fold, reorder, insert, or
rename layers.
Merge.
gh stack merge
gh stack sync --prune
gh stack merge atomically merges the selected layer and every layer below
it. Stop if any selected layer is a draft, has failing checks, or is not
ready.
Finish when the stack matches the confirmed delivery mapping, every submitted
PR has the correct base, and gh stack view --short reports no layer needing a
rebase.