gh-stack skillA
gh-stack is agent-read markdown (skill) from sd0xdev/sd0x-harness: Native stacked pull requests through the github/gh-stack extension. Detects the extension, installs it only after the user approves, resolves the branch chain, and executes `gh stack link` / `gh stack push` / `gh stack submit --auto` under a per-use AskUserQuestion gate. Use when: opening or refreshing a native stack of PRs, linking existing PRs into a stack on GitHub, pushing a stack's branches, or when /create-pr --stack delegates the native path here. Not for: a single PR (use /create-pr), pu.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GH Stack — Native Stacked PRs Wraps the `github/gh-stack` extension so a branch chain becomes a real **Stack** on GitHub — one PR per layer, chained bases, per-layer diff view, linked merges — instead of the hand-built chained-base PR set `/create-pr --stack` produces on its own. ## Authorization ``` ⚠️ This skill is one of the four workflows Anchor Register #4 enumerates (@rules/discretion.md). ⚠️ It may execute exactly three subcommands of the extension — `gh stack link`, `gh stack push`, `gh stack submit --auto` — and nothing else from it, `gh stack view` included: `view` syncs PR metadata and writes it back into `.git/gh-stack`, so it is not a read. What this skill needs to read, it reads without the extension (the first row of the table below). ⚠️ All three push, and they do not push the same way. Read from the extension's source at v0.1.1 (§ Force form): `link` runs a plain `git push --atomic`; `push` and `submit --auto` run a per-branch, value-bearing `git push --force-with-lease=refs/heads/<b>:<sha>`. The approval names the form the chosen subcommand uses. ⚠️ Every `gh stack` invocation REQUIRES explicit per-use user approval via AskUserQuestion …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/gh-stack@git:20260923.6189f54mdr add sd0xdev/sd0x-harness/gh-stack@sha256:5074374c8727e42bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_o43ag3pjfm7pdg44)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (62223 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sd0xdev/sd0x-harness · 189 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o43ag3pjfm7pdg44 GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/gh-stack GET https://markdownregistry.com/api/v1/blob/5074374c8727e42bada83974f8d155f86f0641d7dd2fe5e154addbeebdad0aa0
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from sd0xdev/sd0x-harness
Every file in sd0xdev/sd0x-harness