graphite-workflow

Manage stacked pull requests using Graphite CLI commands.

2|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/jclfocused/claude-agents --skill graphite-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphite-workflow
Source: https://github.com/jclfocused/claude-agents/tree/main/custom_plugins/plugins/linear-planning-workflow/skills/graphite-workflow
Command: npx skills add https://github.com/jclfocused/claude-agents --skill graphite-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures correct usage of the Graphite CLI (gt) for managing stacked Pull Requests, preventing common errors when using raw git commands in a stack-aware workflow.

Core Features & Use Cases

  • Stack-Aware Operations: Use gt commands for creating, modifying, and submitting stacked PRs.
  • Workflow Guidance: Provides clear rules on when to use gt vs. git and outlines best practices for stack building.
  • Use Case: When working on a complex feature broken into multiple small PRs, this Skill guides you to use gt create for each commit, gt submit to push the stack, and gt sync to manage updates, ensuring your PRs are always correctly ordered and rebased.

Quick Start

Use the graphite-workflow skill to create a new stacked PR with the message "feat: implement user login".

Frequently Asked Questions about graphite-workflow

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

FAQPage Schema
How do I manage stacked pull requests using Graphite?

Manage stacked pull requests by using the Graphite CLI (`gt`) to create, modify, submit, and sync branches. This ensures proper integration with Graphite's stack management features for efficient version control.

Why should I use gt commands instead of raw git for stacked PRs?

Use `gt` commands instead of raw `git` for stacked PRs to maintain stack integrity. Raw `git` commands can cause common errors in a stack-aware workflow, whereas `gt` ensures branches are correctly ordered and rebased.

What is the best way to create and submit a stacked PR for a complex feature?

The best way to create and submit a stacked PR is using `gt create` for each commit, `gt submit` to push the stack, and `gt sync` to manage updates. This workflow keeps your PRs correctly ordered and rebased.

Can I use raw git commands when working in a Graphite stacked workflow?

Raw `git` commands should be avoided for stack-related tasks in a Graphite workflow. The Graphite CLI enforces stack-aware operations to maintain integrity, preventing common errors that arise from using raw `git`.

When do I need to use gt sync when working with stacked branches?

Use `gt sync` to manage updates when working with stacked branches. It ensures your stacked pull requests remain correctly ordered and rebased during the version control workflow.

Does the Graphite workflow support breaking a complex feature into multiple small PRs?

Graphite workflow supports breaking complex features into multiple small PRs. It guides you to use `gt create` for each commit and `gt submit` to push the stack, ensuring efficient version control and correct ordering.