graphite

Automate stacked pull request creation, navigation, and management with Graphite.

1|Updated Apr 13, 2015
One-click install
npx skills add https://github.com/tyler-dot-earth/.dotfiles --skill graphite-tyler-dot-earth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphite
Source: https://github.com/tyler-dot-earth/.dotfiles/tree/main/agents/skills/graphite
Command: npx skills add https://github.com/tyler-dot-earth/.dotfiles --skill graphite-tyler-dot-earth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Graphite helps teams manage complex or multi-PR workflows by organizing changes into a coherent stack, enabling focused reviews and staged integration.

Core Features & Use Cases

  • Create, navigate, and reorder a stack of related pull requests
  • Move up/down the stack, jump to top/bottom, and view the full stack structure
  • Submit an entire stack for review and manage parent-child relationships

Quick Start

Start by creating a stack with gt create and then incrementally build and submit PRs with gt up, gt down, and gt submit.

Frequently Asked Questions about graphite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage stacked pull requests for complex multi-branch workflows?

Stacked pull requests organize related changes into a coherent stack for focused reviews. You create a stack with gt create and incrementally build PRs using gt up, gt down, and gt submit.

What is the best way to reorder branches within a pull request stack?

Reordering branches in a pull request stack is handled natively by Graphite commands. You can navigate the stack with gt up and gt down, then apply gt restack to update parent-child relationships across multiple branches.

Can I submit an entire stack of pull requests for review at once?

Yes, submitting an entire stack for review is supported. After building your stack with gt create, you use gt submit to manage parent-child relationships and push the full stack of related pull requests for review simultaneously.

Do I need to use standard git commands alongside Graphite for branch tracking?

Standard git commands are used alongside Graphite for branch tracking and management. The workflow conforms to both gt-specific operations like gt track and gt rename, and underlying git operations to maintain stack structure.

How does navigating up and down a pull request stack work?

Navigating a pull request stack works by moving sequentially through parent-child branch relationships. You use gt up and gt down to move between branches, or jump directly to the top or bottom to view the full stack structure.