gh-stack
Manage Stacked Pull Requests with gh-stack
Dependent pull requests are difficult to organize, update, and merge safely. This skill guides reliable gh-stack workflows for linear branch stacks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gh-stack" from https://skillstore.io/skills/jssblck-gh-stack.md and its manifest at https://skillstore.io/api/skills/jssblck-gh-stack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gh-stack". Plan a stack for authentication, API routes, and interface integration.
Expected outcome:
Create authentication first, API routes second, and interface integration last. Each pull request depends only on reviewed lower layers.
Using "gh-stack". A lower branch changed and every branch above now needs rebasing.
Expected outcome:
- Check out the lower branch and commit the focused change.
- Rebase the branches above it, resolve conflicts, and return to the top.
- Push the stack and verify each pull request.
Using "gh-stack". Local and GitHub stack structures have diverged.
Expected outcome:
Compare both chains, choose the authoritative structure, unlink only the incorrect grouping, then rebuild without deleting branches or pull requests.
Security Audit
SafeAll 68 static findings are false positives caused by Markdown, ordinary prose, or documented Git commands with fixed arguments. The skill intentionally operates Git and GitHub, but no prompt injection, exfiltration, concealed execution, or unsafe command interpolation was found.
Risk Factors
🌐 Network access (4)
⚙️ External commands (50)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/jssblck-gh-stack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/jssblck-gh-stack?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/jssblck-gh-stack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jssblck-gh-stack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/jssblck-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>Academic citations (APA · BibTeX · CFF)
APA citation
jssblck. (2026). gh-stack security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jssblck-gh-stack/audits/1BibTeX citation
@techreport{jssblck-jssblck-gh-stack-2026,
author = {jssblck},
title = {gh-stack security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/jssblck-gh-stack/audits/1},
note = {Author version unspecified}
}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: "unspecified"
type: report
authors:
- name: "jssblck"
date-released: "2026-08-23"
url: "https://skillstore.io/skills/jssblck-gh-stack/audits/1"
identifiers:
- type: other
value: "skillstore:jssblck-gh-stack:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Split a feature for review
Plan backend, interface, and test changes as ordered pull requests with focused diffs.
Maintain an active stack
Update a lower layer, rebase dependent branches, and synchronize remote pull requests.
Recover a disrupted workflow
Diagnose divergence, rebase conflicts, locked state, or interrupted stack modification.
Try These Prompts
Inspect my current gh-stack state and summarize each branch, pull request, and required action.
Plan a gh-stack for [feature]. Separate concerns into reviewable branches and explain their bottom-to-top dependency order.
Move [change] into its owning branch, commit it, rebase every dependent layer, and verify the resulting stack.
Diagnose [stack problem], preserve existing branches and pull requests, recover non-interactively, then merge only [target scope] after verification.
Best Practices
- Create the stack before editing files and keep one concern in each layer.
- Use explicit remote names and non-interactive flags for agent workflows.
- Inspect machine-readable stack state before and after mutating operations.
Avoid
- Do not implement everything on one branch and split it afterward.
- Do not commit a lower layer concern on the top branch.
- Do not run interactive stack commands in unattended agent sessions.
Frequently Asked Questions
What is a stacked pull request?
Does this skill install gh-stack?
Can it manage multiple remotes?
Can it reorder stack layers automatically?
How are rebase conflicts handled?
Does merging always bypass repository rules?
Developer Details
Author
jssblckLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/jssblck/agents/tree/4658295e88faed205cc134edf987f7ea4e0c8ea4/skills/gh-stackRef
88347d33645a3df8196bc00b997174902b742a6f
Maintenance freshness
8/23/2026
Usage
0 downloads · 0 views
File structure