atmos: Skill for Claude Code

GitHub PR stacks

Use this skill for dependent pull requests. Read maintenance and recovery before changing an existing published stack or operating its CI/review queue. Use the pull-request skill for labels, signing, descriptions, and release documentation.

Discover the tool and the actual stack

Start with gh stack --help and the relevant subcommand's --help; commands and supported flags can change. If the extension is missing, identify github/gh-stack as the required extension (gh extension install github/gh-stack). Follow the environment's installation permissions; do not silently replace native stacks with an unregistered branch chain.

A feature branch based on another feature branch is only a dependency chain. GitHub's native stack is a separate object. Creating PRs with gh pr create --base <parent> alone does not register that object. Check both the configured base branches and native stack membership. A bottom PR may target main and still belong to a stack; also look for open PRs based on its head branch.

When native registration is requested or otherwise authorized, use gh stack link for existing PRs in the intended bottom-to-top order. Inspect current remote membership first, since linking changes the stack. Do not convert an ordinary chain into a native stack merely to inspect it. Verify the resulting object and ordering on GitHub, not just local branch ancestry. For example, after substituting the actual repository and PR number:

gh stack link <bottom-pr> <middle-pr> <top-pr>
gh api graphql -f query='{ repository(owner:"OWNER", name:"REPO") {
  pullRequest(number:123) { stack { number size entries(first:100) {
    nodes { position pullRequest { number } }
  } } }
} }'

Paginate if the returned entries do not cover the reported size. gh stack link can register remote PRs without initializing local tracking; a local gh stack view failure alone does not prove the remote stack is absent. Inspect the installed checkout/link help to reconcile local tracking.