Stacked PR workflow with the Graphite CLI (gt) — create stacks, submit, sync, restack, split/squash/fold, track existing branches, collaborate on shared stacks, configure repo/CI for Graphite, and operate the merge queue.
70
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Move to a different branch in the Graphite stack. User input: $ARGUMENTS.
up or empty + "next up" intent → gt up (alias gt u); accept a trailing number for steps (gt up 2).down → gt down (gt d); same step semantics.top → gt top (gt t).bottom → gt bottom (gt b).trunk or main → gt checkout --trunk (gt co -t).gt checkout <name> (gt co <name>).gt checkout (interactive picker — only run if the session supports interactive prompts; otherwise show gt ls and ask the user to pick).git status --short and confirm with the user — checkout will fail or carry the changes.gt ls to show context.gt ls (the new current branch is marked ◉).gt up or gt top hits a branch with multiple children, it prompts to disambiguate. In non-interactive contexts, pass the specific branch name instead.gt checkout -s <branch> switches to a branch and pulls its whole stack — useful when navigating to a teammate's stack after gt get.