gh-stack

Topics in the source

• Choose the path
• Build or maintain

Fetch a named PR first. Inspect its base, head, and downstack PRs with the official GitHub MCP; a branch name or installed extension alone does not establish a stack. Keep changes small and independently reviewable. Use gh stack when dependent PRs form a stack; one independent PR uses the normal GitHub workflow. The dotfiles repository deploys without PRs. Check gh stack --help for extension availability and gh stack view --json for a locally tracked stack. If unavailable or untracked, do not assume stack metadata; inspect PRs through the MCP. Run CLI operations through Bash, not Eval. Initialize local tracking only from a clean checkout whose branches are not checked out in other worktrees: gh stack init --base ... adopts existing branches or creates missing ones in bottom-to-top order. gh stack add adds above the current layer. Verify branch ancestry and intended PR bases. Create or edit individual PRs with the official GitHub MCP. Set the bottom PR base to trunk and each higher PR base to the branch below. Preserve existing draft and reviewer state. To register existing PRs without local tracking, use gh stack link ... only after verifying each member and base. Use PR URLs/numbe

This is an excerpt. Refer to the complete source and its current requirements.