graphite-stacked-diffs

Automates stacked pull request management using the Graphite CLI.

1|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill graphite-stacked-diffs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphite-stacked-diffs
Source: https://github.com/pascallammers/mylo-travel-concierge-v2/tree/main/.claude/skills/graphite-stacked-diffs
Command: npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill graphite-stacked-diffs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the complex workflow of managing multiple, dependent pull requests (stacked PRs) using the Graphite CLI, ensuring efficient code reviews and continuous integration.

Core Features & Use Cases

  • Stack Creation & Management: Guides users through creating, submitting, and updating stacks of PRs.
  • Automated Rebasing: Handles complex rebasing and conflict resolution automatically as changes propagate through the stack.
  • Workflow Optimization: Enables parallel development and keeps developers unblocked while waiting for reviews on earlier PRs in the stack.
  • Use Case: A developer needs to implement a new feature that touches the database, API, and frontend. They can break this into three separate PRs (DB changes, API endpoints, UI implementation) and manage them as a stack, allowing for independent review and faster iteration.

Quick Start

Use the graphite-stacked-diffs skill to create a new stacked pull request with the message "feat(api): Add user endpoints".

Frequently Asked Questions about graphite-stacked-diffs

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

FAQPage Schema
How do I manage stacked pull requests in Git for parallel development?

Managing stacked pull requests in Git involves creating, submitting, and updating dependent changes across multiple PRs. This Skill automates that workflow using the Graphite CLI, enabling parallel development and keeping developers unblocked while waiting for code reviews.

What is the best way to handle rebasing and conflict resolution across a stack of PRs?

Handling rebasing across a stack of PRs is easiest when automated. This Skill uses the Graphite CLI to automatically rebase dependent changes and resolve conflicts as updates propagate through the stack, ensuring continuous integration without manual intervention.

Can I break down a large feature into smaller pull requests for independent code review?

Yes, you can break down a large feature into smaller pull requests for independent code review. This Skill guides you through creating a stack of dependent PRs, allowing teams to review database, API, and frontend changes separately for faster iteration.

Do I need the Graphite CLI to automate stacked diffs and continuous integration?

Yes, the Graphite CLI is required to automate stacked diffs and continuous integration. This Skill facilitates the creation and merging of dependent changes by interfacing directly with the Graphite CLI to streamline your Git workflow.

Why use stacked PRs instead of a single large pull request for complex feature development?

Stacked PRs are used instead of a single large pull request to enable parallel development and keep developers unblocked. This approach addresses the need for streamlined Git workflows in complex feature development by allowing independent review of dependent changes.

When should I avoid using stacked pull requests in my developer workflow?

You should avoid using stacked pull requests when your feature changes are not dependent on each other or when your team's code review process cannot handle dependent changes across multiple PRs. This Skill targets complex feature development requiring streamlined Git workflows.