Use this skill when working with Graphite (gt) for stacked PRs, using execute-issue-graphite agent, or when the user mentions Graphite, stacking, or gt commands...
This skill ensures correct usage of Graphite CLI (gt) for managing stacked PRs. When working in a Graphite-enabled workflow, always use gt commands instead of raw git commands for stack-aware operations.
Apply this skill when:
gtexecute-issue-graphite agent| Instead of... | Use... | Why |
|---|---|---|
git commit |
gt create -a -m "message" |
Creates branch + commit + tracks in stack |
git commit --amend |
gt modify -a |
Amends AND auto-restacks descendants |
git push |
gt submit --no-interactive |
Pushes AND creates/updates PRs |
git checkout <branch> |
gt checkout <branch> |
Stack-aware checkout |
git pull / git rebase |
gt sync |
Syncs trunk AND rebases entire stack |
# Creating PRs in a stack
gt create -a -m "feat: description" # Stage all, create branch, commit
# Modifying existing PR
gt modify -a # Amend commit, auto-restack upstack
# Submitting to GitHub
gt submit --no-interactive # Current branch + downstack
gt submit --stack --no-interactive # Entire stack
# Navigation
gt up / gt down # Move within stack
gt top / gt bottom # Jump to ends of stack
gt checkout # Interactive picker
# Syncing
gt sync # Fetch trunk, rebase stack, cleanup merged
# Viewing
gt log # Visual stack graph
gt ls # Short list
git add .gt create -a -m "message"gt submit --stack --no-interactiveThese operations are fine with raw git:
git add - Staging filesgit status - Checking statusgit diff - Viewing changesgit log (for viewing history, not stack structure)When changes are needed to an earlier PR in the stack:
gt checkout <branch-needing-changes>
# Make code changes
git add .
gt modify -a # Amend + auto-restack
gt submit --stack --no-interactive # Push updates
# If conflict occurs during sync/restack:
# 1. Fix conflicts in editor
git add .
gt continue
# To abort:
gt abort