How do I install the Graphite Workflow skill?

Run npx skillmds@latest add majiayu000/graphite-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Graphite Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Graphite Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Graphite Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Graphite Workflow?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Graphite Workflow by majiayu000 — Agent Skill

Name: Graphite Workflow
Rating: 4.2 (5 reviews)
Author: majiayu000

Graphite Workflow

Use this skill when working with Graphite (gt) for stacked PRs, when the user mentions pull requests, Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware operations.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Graphite Workflow Skill

This skill ensures correct usage of Graphite CLI (gt) for managing stacked PRs. When working in a Graphite-enabled workflow, always use gt commands instead of raw git commands for stack-aware operations.

When to Use

Apply this skill when:

User mentions Graphite, pull requests, stacking, or gt
Working on a feature that uses stacked PRs
Managing branches in a stack

Critical Rule: gt vs git

Instead of...	Use...	Why
`git commit`	`gt create -a -m "message"`	Creates branch + commit + tracks in stack
`git commit --amend`	`gt modify -a`	Amends AND auto-restacks descendants
`git push`	`gt submit --no-interactive`	Pushes AND creates/updates PRs
`git checkout <branch>`	`gt checkout <branch>`	Stack-aware checkout
`git pull` / `git rebase`	`gt sync`	Syncs trunk AND rebases entire stack

Core Commands Quick Reference

# Creating PRs in a stack
gt create -a -m "feat: description"   # Stage all, create branch, commit

# Modifying existing PR
gt modify -a                           # Amend commit, auto-restack upstack

# Submitting to GitHub
gt submit --no-interactive             # Current branch + downstack
gt submit --stack --no-interactive     # Entire stack

# Navigation
gt up / gt down                        # Move within stack
gt top / gt bottom                     # Jump to ends of stack
gt checkout                            # Interactive picker

# Syncing
gt sync                                # Fetch trunk, rebase stack, cleanup merged

# Viewing
gt log                                 # Visual stack graph
gt ls                                  # Short list

The Stack Building Workflow

Write code FIRST - Never create empty branches
Stage changes - git add .
Create branch - gt create -a -m "message"
Repeat for each slice
Submit stack - gt submit --stack --no-interactive

When to Use Raw Git

These operations are fine with raw git:

git add - Staging files
git status - Checking status
git diff - Viewing changes
git log (for viewing history, not stack structure)

Handling Modifications

When changes are needed to an earlier PR in the stack:

gt checkout <branch-needing-changes>
# Make code changes
git add .
gt modify -a                           # Amend + auto-restack
gt submit --stack --no-interactive     # Push updates

Conflict Resolution

# If conflict occurs during sync/restack:
# 1. Fix conflicts in editor
git add .
gt continue

# To abort:
gt abort

---name: graphite-workflowdescription: Use this skill when working with Graphite (gt) for stacked PRs, when the user mentions pull requests, Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware operations.--- # Graphite Workflow Skill This skill ensures correct usage of Graphite CLI (`gt`) for managing stacked PRs. When working in a Graphite-enabled workflow, **always use `gt` commands instead of raw `git` commands** for stack-aware operations. ## When to Use Apply this skill when: - User mentions Graphite, pull requests, stacking, or `gt` - Working on a feature that uses stacked PRs - Managing branches in a stack ## Critical Rule: gt vs git | Instead of... | Use... | Why | |---------------|--------|-----| | `git commit` | `gt create -a -m "message"` | Creates branch + commit + tracks in stack | | `git commit --amend` | `gt modify -a` | Amends AND auto-restacks descendants | | `git push` | `gt submit --no-interactive` | Pushes AND creates/updates PRs | | `git checkout <branch>` | `gt checkout <branch>` | Stack-aware checkout | | `git pull` / `git rebase` | `gt sync` | Syncs trunk AND rebases entire stack | ## Core Commands Quick Reference ```bash # Creating PRs in a stack gt create -a -m "feat: description" # Stage all, create branch, commit # Modifying existing PR gt modify -a # Amend commit, auto-restack upstack # Submitting to GitHub gt submit --no-interactive # Current branch + downstack gt submit --stack --no-interactive # Entire stack # Navigation gt up / gt down # Move within stack gt top / gt bottom # Jump to ends of stack gt checkout # Interactive picker # Syncing gt sync # Fetch trunk, rebase stack, cleanup merged # Viewing gt log # Visual stack graph gt ls # Short list ``` ## The Stack Building Workflow 1. **Write code FIRST** - Never create empty branches 2. **Stage changes** - `git add .` 3. **Create branch** - `gt create -a -m "message"` 4. **Repeat** for each slice 5. **Submit stack** - `gt submit --stack --no-interactive` ## When to Use Raw Git These operations are fine with raw git: - `git add` - Staging files - `git status` - Checking status - `git diff` - Viewing changes - `git log` (for viewing history, not stack structure) ## Handling Modifications When changes are needed to an earlier PR in the stack: ```bash gt checkout <branch-needing-changes> # Make code changes git add . gt modify -a # Amend + auto-restack gt submit --stack --no-interactive # Push updates ``` ## Conflict Resolution ```bash # If conflict occurs during sync/restack: # 1. Fix conflicts in editor git add . gt continue # To abort: gt abort ```

Frequently asked questions