스킬 gh-stack
📦

gh-stack

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

4
스캔된 파일
693
분석된 줄 수
0
검토 항목
0
오탐 무시됨

위험 요인

⚙️ 외부 명령어 (50)
references/commands.md:202 references/troubleshooting.md:101 references/troubleshooting.md:102 SKILL.md:15 SKILL.md:19 SKILL.md:21-23 SKILL.md:23-25 SKILL.md:25 SKILL.md:26 SKILL.md:28-34 SKILL.md:34-38 SKILL.md:38-42 SKILL.md:42-46 SKILL.md:46 SKILL.md:47 SKILL.md:48-52 SKILL.md:52 SKILL.md:53 SKILL.md:54 SKILL.md:55 SKILL.md:56 SKILL.md:57 SKILL.md:58 SKILL.md:59-61 SKILL.md:61 SKILL.md:62-63 SKILL.md:63-64 SKILL.md:64-65 SKILL.md:65-74 SKILL.md:74-75 SKILL.md:75-78 SKILL.md:78-84 SKILL.md:84-88 SKILL.md:88-95 SKILL.md:95-97 SKILL.md:97 SKILL.md:98 SKILL.md:102-105 SKILL.md:105-107 SKILL.md:107-108 SKILL.md:108 SKILL.md:109-115 SKILL.md:115-119 SKILL.md:119-131 SKILL.md:131-134 SKILL.md:134-139 SKILL.md:139-141 SKILL.md:141-142 SKILL.md:142-151 SKILL.md:151
🌐 네트워크 접근 (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 근거로 순위가 정해집니다.

이 변형이 1위인 이유

Skillstore 점수가 가장 높음
github 권장 현재

github-gh-stack

Skillstore 점수 79
증거 신뢰도 중간
Skillstore 사용량 16
업데이트됨

2026-10-06

jssblck

jssblck-gh-stack

Skillstore 점수 76
증거 신뢰도 중간
Skillstore 사용량 7
업데이트됨

2026-09-09

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간
45
아키텍처
100
유지보수성
87
콘텐츠
65
커뮤니티
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.

개발자 세부 정보

작성자

github

라이선스

MIT

작성자 버전

v0.2.0

Skillstore 리비전

r1

리포지토리

https://github.com/github/gh-stack/tree/d4ab7ab47e5b3e3708a27c8c42abcdf4bc321419/skills/gh-stack

참조

5fa1d077e6c44bb8da33885064d2b6c190282c6e

유지보수 최신성

2026. 10. 6.

사용량

1 다운로드 · 0 조회

파일 구조

📁 references/

📄 commands.md

📄 stack-design.md

📄 troubleshooting.md

📄 SKILL.md

github의 다른 스킬

전체 보기

관련 스킬

전체 보기