use-graphite

Block conflicting git and gh commands in Graphite-managed repositories.

4|Updated Dec 14, 2025

Search Tags:#git #workflow #pr #graphite #blocker #stacked-prs

Ready to run

npx skills add https://github.com/LukasStrickler/ai-dev-atelier --skill use-graphite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: use-graphite
Source: https://github.com/LukasStrickler/ai-dev-atelier/tree/main/content/skills/use-graphite
Command: npx skills add https://github.com/LukasStrickler/ai-dev-atelier --skill use-graphite

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Graphite enables teams to manage large changes as a sequence of dependent PRs, preventing unreviewable or conflicting pushes by guiding users to Graphite-aware commands.

Core Features & Use Cases

Detects active Graphite workflows and blocks conflicting git/gh actions until a Graphite command is used.
Provides safe alternatives for creating branches, pushing commits, and submitting PRs in stacked workflows.
Enables incremental development for large features, migrations, or refactors by maintaining a clean PR stack.

Quick Start

Load the Graphite workflow by running the detection script and following prompts. Then start using Graphite-friendly commands such as gt create, gt submit, and gt restack instead of git push, gh pr create, or git branch.

Frequently Asked Questions about use-graphite

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

FAQPage Schema

How do I split a large git change into a stacked PR workflow?▼

Graphite manages large changes by splitting them into a sequence of dependent PRs, guiding you to use Graphite-aware commands like gt create and gt submit instead of standard git push. This maintains a clean, reviewable PR stack for incremental development.

Why does git push or gh pr create get blocked in my repository?▼

Git push and gh pr create are blocked because the Graphite workflow intercepts conflicting git and gh commands to prevent unreviewable pushes. It guides you to Graphite-safe alternatives like gt submit to maintain stack alignment in a Graphite-managed repository.

What are Graphite-safe alternatives to git branch and gh pr create?▼

Graphite-safe alternatives include using gt create to start new branches and gt submit for creating PRs. These commands replace git branch and gh pr create, ensuring actions remain stack-aligned and prevent conflicts within a Graphite-managed repository.

Do I need the Graphite CLI to manage stacked PRs?▼

Yes, you need the Graphite CLI and its repository configuration to manage stacked PRs. The workflow relies on the Graphite CLI to intercept standard git and gh commands, providing safe, stack-aligned actions for large feature migrations and refactors.

When should I use stacked PRs instead of a single large pull request?▼

You should use stacked PRs for large features, migrations, or refactors that would otherwise be unreviewable as a single pull request. Graphite enables incremental development by managing these large changes as a sequence of dependent PRs.