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
create.mdcommands/
- description:
- Create a new stacked branch from the current changes (gt create)
- allowed-tools:
- Bash, Read, Grep
- argument-hint:
- branch-name or commit message
Create a new Graphite-tracked branch on top of the current branch, carrying the working-tree changes as a single commit. User input: $ARGUMENTS.
Steps
- Run
git status --shortto confirm there are changes to commit. If the tree is clean, ask the user whether they meant to rungt create --onto <branch>(create empty branch on top of another). - Run
gt lsto show the current stack so the user can confirm where the new branch lands. - Build the command:
- If
$ARGUMENTSlooks like a commit message (contains spaces or:), usegt create -am "$ARGUMENTS"— Graphite derives the branch name from the message. - If
$ARGUMENTSis a single token, treat it as a branch name. Ask the user for a commit message, then run:gt create -am "<message>" $ARGUMENTS. - If
$ARGUMENTSis empty, ask the user for a commit message (or branch name) before proceeding.
- If
- Run the command and report the new branch and updated
gt ls.
Key flags
-a, --all— stage every modified file (default for this command)-m, --message <msg>— commit message (and source of the auto-generated branch name)-p, --patch— interactive hunk staging instead of-a--insert— insert this branch between the current branch and its children, restacking dependents--onto <branch>— create on top of a different branch (useful with worktrees)--ai— let Graphite suggest a branch name / message