gh-stack
Manage Stacked GitHub Pull Requests
Large changes become difficult to review when unrelated concerns share one branch. This skill guides dependency-based branch planning and non-interactive stacked PR workflows.
使用我的智能体安装
将此请求复制给你的智能体,其中包含权威 Skill 页面和清单。
Review the Skillstore skill "gh-stack" from https://skillstore.io/skills/github-gh-stack.md and its manifest at https://skillstore.io/api/skills/github-gh-stack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划,并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文,而不是读取完整页面时,请使用这些链接。
测试它
正在使用“gh-stack”。 Plan a stack for a billing feature with schema, API, and interface changes.
预期结果:
- Proposed order: main, billing/schema, billing/api, billing/ui.
- The schema layer defines shared data; the API depends on it; the interface depends on the API.
- Each branch contains one review concern. No branches have been created.
正在使用“gh-stack”。 The sync command returned success but reported Sync aborted. What should I check?
预期结果:
- The documented divergence path can return exit code zero without synchronizing.
- Compare local and remote branch chains and inspect the stack again.
- Choose which composition to keep before resetting tracking or recreating the GitHub grouping.
正在使用“gh-stack”。 I changed API code while working on the frontend branch.
预期结果:
- Inspect stack state and file history to identify the owning API layer.
- Move to the correct owning worktree and stage only the API change.
- After committing, rebase dependent branches and verify the stack before requesting approval to push.
安全审计
安全All 72 static findings are false positives from Markdown formatting, ordinary prose, a documentation link, or safe Git command substitutions. No evidence found of prompt injection, credential theft, or unauthorized exfiltration in the four reviewed files. The documented workflow still installs an external extension, modifies Git state, and publishes or merges changes through GitHub.
风险因素
⚙️ 外部命令 (50)
🌐 网络访问 (3)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据,不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/github-gh-stack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/github-gh-stack?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/github-gh-stack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/github-gh-stack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/github-gh-stack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
github. (2026). gh-stack security audit report (audit version 1) [Author version 0.2.0]. Skillstore. https://skillstore.io/skills/github-gh-stack/audits/1BibTeX 引用
@techreport{github-github-gh-stack-2026,
author = {github},
title = {gh-stack security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/github-gh-stack/audits/1},
note = {Author version 0.2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gh-stack security audit report (audit version 1)"
version: "0.2.0"
type: report
authors:
- name: "github"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/github-gh-stack/audits/1"
identifiers:
- type: other
value: "skillstore:github-gh-stack:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中你能构建什么
Split a Feature Into Reviewable Layers
Plan schema, API, and interface branches in dependency order, then submit a linked set of draft pull requests.
Update a Shared Lower Layer
Find the branch that owns a change, commit there, and rebase dependent branches while respecting worktree ownership.
Automate Stack Maintenance
Use explicit targets, structured output, remote selection, and documented recovery paths to maintain stacks without interactive menus.
试试这些提示
Inspect my current gh-stack state. Summarize branch order, pull request status, and rebase needs without changing branches or publishing anything.
Plan a stack for [feature]. Propose dependency-ordered branches using repository naming conventions. Explain each review scope and wait for approval before creating branches.
Place [change] in its owning branch. Inspect ownership and worktree state, propose targeted staging and upstack rebasing, and request approval before remote updates.
Diagnose divergence between my local and GitHub stacks. Compare both chains, explain recovery options, and preserve branches. Await approval before regrouping or publishing.
最佳实践
- Plan branch dependencies before implementation and stage only the files belonging to each layer.
- Select the intended remote explicitly and review publication or merge scope before approving remote changes.
- Use structured view output, verify exit status, and resolve conflicts in the reported owning worktree.
避免
- Implement every concern on one branch and expect stack metadata alone to split or reorder commits.
- Invoke interactive menus from automation or parse human-readable status messages as structured stack state.
- Assume exit code zero proves synchronization completed when the output reports Sync aborted.
常见问题
What must be installed before using this skill?
Can Claude and Codex use this skill?
Does pushing a stack create pull requests?
Are new pull requests drafts?
Can this skill reorder branches without interaction?
Does this workflow change local or remote data?
开发者详情
作者
github许可证
MIT
作者版本
v0.2.0
Skillstore 修订
r1
引用
5fa1d077e6c44bb8da33885064d2b6c190282c6e
维护新鲜度
2026/10/6
使用量
0 次下载 · 0 次浏览
文件结构