📦

gh-stack

Name: gh-stack
Author: github

v0.2.0 コンテンツリビジョン r1 安全 ⚙️ 外部コマンド🌐 ネットワークアクセス

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.

対応: Claude Codex Code(CC)

🥉 79 ブロンズ

Maintain this Skill? Claim it 🥉 79 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の 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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/github-gh-stack.md 署名済み manifest GET /api/skills/github-gh-stack/manifest 署名済み lockfile GET /api/skills/github-gh-stack/lockfile

テストする

「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.

セキュリティ監査

安全

v1 • 2026/10/5 バージョン別レポートを開く

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.

スキャンされたファイル

693

解析済み行数

レビュー項目

誤検知を無視

リスク要因

⚙️ 外部コマンド (50)

🌐 ネットワークアクセス (3)

references/commands.md:60 SKILL.md:16 SKILL.md:15

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/github-gh-stack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/github-gh-stack/security.svg)](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/1

BibTeX形式の引用

@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"

バリアントを比較

インストール可能なバリアント 2 件

各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。

このバリアントが首位の理由

Skillstore スコアが最高

作者 / ソース Skillstore スコア証拠の信頼度 Skillstore 利用状況更新済み

github 推奨現在

github-gh-stack

Skillstore スコア 79

証拠の信頼度中

Skillstore 利用状況 16

更新済み

2026-10-06

jssblck

jssblck-gh-stack

Skillstore スコア 76

証拠の信頼度中

Skillstore 利用状況 7

更新済み

2026-09-09

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

100

保守性

コンテンツ

コミュニティ

100

仕様準拠

作成できるもの

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 an Existing Stack

Inspect my current gh-stack state. Summarize branch order, pull request status, and rebase needs without changing branches or publishing anything.

Plan a New Feature Stack

Plan a stack for [feature]. Propose dependency-ordered branches using repository naming conventions. Explain each review scope and wait for approval before creating branches.

Edit the Correct Layer

Place [change] in its owning branch. Inspect ownership and worktree state, propose targeted staging and upstack rebasing, and request approval before remote updates.

Recover and Publish a Diverged Stack

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?

Install Git 2.36 or later, authenticate GitHub CLI, and install the gh-stack extension. The skill provides guidance rather than the extension implementation.

Can Claude and Codex use this skill?

The skill supports Claude, Codex, and Claude Code. Command execution requires a compatible environment with the necessary tools and repository access.

Does pushing a stack create pull requests?

No. Push updates active branches. Submit pushes branches, creates missing pull requests, and links them into a GitHub stack.

Are new pull requests drafts?

Submit creates draft pull requests by default. The open flag marks new and existing pull requests ready for review.

Can this skill reorder branches without interaction?

There is no non-interactive in-place reorder. Correct Git ancestry first, then rebuild stack tracking; metadata changes alone do not reorder commits.

Does this workflow change local or remote data?

Yes. Commands can install an extension, configure Git, rewrite history, publish branches, merge PRs, and prune merged local branches when explicitly requested.