📦

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-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

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 • 05.10.2026 Открыть версионный отчет

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.