graphite

A Git workflow guide for using Graphite, a command-line tool for managing stacked branches and pull requests.

In plain words
What is it for?
Creating and modifying branches and commits, restacking dependent work, and submitting pull requests through Graphite.
Why use it?
It keeps branch-stack information consistent when creating branches, changing commits, restacking work, or opening pull requests.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/usefulsoftwareco/executor/graphite
Any agent
npx skills add UsefulSoftwareCo/executor --skill graphite
Clone the repo
git clone --depth 1 https://github.com/UsefulSoftwareCo/executor

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,861 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.02861
Opus 5 $0.00034 $0.01430
Sonnet 5 $0.00014 $0.00572
Haiku 4.5 $0.00007 $0.00286

Measured 2d ago against content hash 6f6c8e5ee323, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

graphite scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • graphite — 100% identical, 0 lines differ
.skills/graphite/SKILL.md · 413 lines

How it starts

The opening of the file, as written. The whole thing — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Graphite CLI Command Reference

Prefer gt over git

Use gt commands instead of their git counterparts for commit and branch management. Raw git bypasses Graphite's stack metadata, leaving descendants un-restacked and the CLI's view of the stack out of sync.

Instead of Use
git checkout -b <name> gt create <name>
git commit -m "msg" gt modify -c -m "msg"
git commit --amend gt modify --amend
git commit -am "msg" gt modify -cam "msg"

Why: gt keeps stack metadata consistent and auto-restacks descendant branches when a parent changes.

Interactivity (for agents)

Several commands are interactive by default and will hang without a TTY: gt modify, gt move, gt split, gt restack, gt checkout (no arg), gt submit.

  • Always pass explicit args/flags: gt move --onto <branch>, gt modify -m "msg", gt checkout <branch>, gt submit --no-interactive.
  • Add --no-interactive (or --quiet) to skip prompts.
  • If a command genuinely needs input that can't be supplied via flags (e.g. complex rebase conflict resolution), stop and notify the user rather than guessing.

Rebase Conflicts

When gt restack, gt move, gt sync, etc. pause on a conflict:

  1. git status to find conflicted files.
  2. Resolve the <<<<<<< / ======= / >>>>>>> markers.
  3. Stage with gt add -A (or git add <file>).
  4. Run gt continuenever git rebase --continue. Graphite tracks its own rebase state; using raw git desyncs it.
  5. Verify the stack once continue completes (gt log, run tests).

To bail out: gt abort.

Global Flags

  • --help - Show help for a command
  • --cwd - Working directory for operations
  • --debug - Write debug output
  • --interactive / --no-interactive - Enable/disable prompts (default: enabled)
  • --verify / --no-verify - Enable/disable git hooks (default: enabled)
  • --quiet - Minimize output, implies --no-interactive

Read the full file on GitHub · 413 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 413 lines · 68 tokens per session scan A 6f6c8e5ee323

Subscribe to this mod's changes

graphite is a skill published in the GitHub repository UsefulSoftwareCo/executor (3,466 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 2,861 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens