Graphite

Teaches Claude to manage stacked PRs using Graphite's CLI, covering the full workflow from creating branches to submitting and updating pull requests. The skill emphasizes creating small, atomic PRs (arguing for more rather than fewer) and includes solid guidance on naming conventions, navigating stacks, and handling common issues like untracked branches in worktrees. Notable for its practical troubleshooting section and the smart workaround for PR descriptions using temporary files instead of heredocs to avoid shell escaping issues with markdown. The advanced rebasing section is genuinely useful if you're dealing with complex nested stacks where gt restack becomes too aggressive.

skills.sh installs: 10K
GitHub stars: 7
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add withgraphite/agent-skills --skill graphite --agent claude-code

Installs into .claude/skills of the current project.

Files

Graphite Skill

Work with Graphite (gt) for creating, navigating, and managing stacked pull requests.

Quick Reference

I want to...	Command
Create a new branch/PR	`gt create branch-name -m "message"`
Amend current branch	`gt modify -m "message"`
Navigate up the stack	`gt up`
Navigate down the stack	`gt down`
Jump to top of stack	`gt top`
Jump to bottom of stack	`gt bottom`
View stack structure	`gt ls`
Submit stack for review	`gt submit --no-interactive`
Rebase stack on trunk	`gt restack`
Change branch parent	`gt track --parent <branch>`
Rename current branch	`gt rename <new-name>`
Move branch in stack	`gt move`

What Makes a Good PR?

In roughly descending order of importance:

Atomic/hermetic - independent of other changes; will pass CI and be safe to deploy on its own
Narrow semantic scope - changes only to module X, or the same change across modules X, Y, Z
Small diff - (heuristic) small total diff line count

Do NOT worry about creating TOO MANY pull requests. It is always preferable to create more pull requests than fewer.

SKILL.md on GitHub