Menu
Manage stacked PR workflows with Graphite CLI in Graphite-enabled repos only; supports autonomous coordinator/workmux execution.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | graphite |
| description | Manage stacked PR workflows with Graphite CLI in Graphite-enabled repos only; supports autonomous coordinator/workmux execution. |
| disable-model-invocation | true |
| allowed-tools | Read, Bash, Glob, Grep |
Use this skill for stacked PR workflows with gt.
This skill applies only when the current repository is Graphite-enabled.
git rev-parse --is-inside-work-tree >/dev/null 2>&1 && \
test -f "$(git rev-parse --git-common-dir)/.graphite_repo_config"
git commit, git push, git rebase, etc.).Do not run gt commands in repos that fail this check.
This skill must work in delegated background flows (for example /coordinator, /worktree, or workmux send ...).
Before implementation, define a small PR stack:
Suggested plan format:
PR Stack for <feature>
1. <pr-1-name>: <goal>
2. <pr-2-name>: <goal>
3. <pr-3-name>: <goal>
In interactive sessions, ask for confirmation only if the stack shape is materially ambiguous.
When Graphite is enabled, prefer gt over direct git branch/stack operations:
gt create -am "<message>"gt modify -agt submit --no-interactivegt sync (or gt restack when needed)gt checkout <branch>Use standard git commands for read-only inspection as needed (git status, git diff, git log).
gt create -am "..." for a new atomic step in the stack.gt modify -a for follow-up edits to the current PR (review feedback, missed files, fixes).gt sync
# implement next atomic step
gt create -am "feat: <message>"
# repeat for next steps
gt submit --no-interactive
If gt sync/gt restack conflicts:
gt continue -a
If recovery is needed:
gt abort
gt log, gt lsgt up, gt down, gt top, gt bottomgt move --onto <branch>, gt split, gt fold, gt squash, gt reorderControl Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, terminals, commands, or communication with another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
Compact the current conversation into a handoff document for another agent to pick up.
Use when the user says "tuicr review", "/tuicr", "open tuicr", or asks to review local changes in tuicr. Launch tuicr in tmux, then use tuicr's review CLI to read or add comments in TUI review sessions.
Investigate aube package-manager trust, provenance, advisory, or install failures before adding bypasses or package exceptions. Use when `aube install`, `aube add`, `aube audit`, or `mise install` with `npm.package_manager = "aube"` fails on trust policy, provenance, advisories, lifecycle scripts, low downloads, lockfile drift, or another supply-chain gate; also use before adding `trustPolicyExclude`, turning `trustPolicy` off, allowing package builds, or accepting npm packages installed through mise.
Always use this skill for PR creation. Use whenever the user asks to open, create, draft, prepare, or submit a pull request, unless they explicitly ask for raw CLI/API commands instead.
Attach an issue or attach a ticket by creating a Platform Linear issue for a PDQ PR or unpushed branch, renaming the branch when needed, updating the PR title, and rerunning the ticketing check.