PluginPublic
pleaseai/graphite
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.
Quality
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
move.mdcommands/
- description:
- Rebase the current branch (and its dependents) onto a new parent (gt move)
- allowed-tools:
- Bash, Read
- argument-hint:
- --onto <branch> | --only
Re-parent the current branch onto a different branch and bring its descendants along. User input: $ARGUMENTS.
Steps
- Run
gt lsto show the current shape. - Determine the target parent:
- If
$ARGUMENTSincludes--onto <branch>or just a branch name, use that. - Otherwise, run
gt moveto open the interactive parent picker. If the session is non-interactive, ask the user for the target branch.
- If
- Run
gt move --onto <target-branch>. - Graphite rebases the current branch onto the target and restacks everything upstack of it. Resolve conflicts the usual way:
gt add .→gt continue -a, orgt abort. - Run
gt lsto confirm the new structure.
Key flags
-o, --onto <branch>— target parent (skips interactive picker)--only— move just this branch; do not bring children along
When to use vs reorder
- Single branch + clear new parent →
gt move --onto. - Multiple branches need shuffling →
/graphite:reorder(editor-based). - Just inserting a new branch →
/graphite:createwith--insert.