Graphite is a developer workflow platform built on top of GitHub that helps engineering teams ship code faster through stacked pull requests, an AI code reviewer (Graphite Agent), and a stack-aware merge queue. Using its CLI, VS Code extension, and web app, developers break large features into small, dependent PRs that can be reviewed in parallel instead of waiting on massive branches. It's used by teams at Shopify, Ramp, Vercel, and Asana to reduce review time and keep engineers unblocked.

• Stacked Pull Requests: Create dependent PRs without waiting for upstream merges. The CLI handles rebasing and syncing across your stack automatically.
• Graphite Agent (AI Code Review): An AI-powered code reviewer that analyzes pull requests, finds potential bugs, explains issues, and suggests fixes directly inside the review workflow.
• Stack-Aware Merge Queue: Batches and merges stacked PRs in order, keeps branches green, and lands changes on autopilot once approved.
• PR Inbox: A unified inbox for all your review requests and PRs, designed around an inbox-zero workflow.
• Insights & Dev Metrics: Dashboards that track review time, PR size, and other productivity signals to help identify workflow bottlenecks.
• VS Code Extension & CLI (gt): Interactive Git views, keyboard shortcuts, and commands like gt create, gt submit, and gt sync for managing stacks.
• Integrations: Native GitHub sync plus Slack notifications, Linear, and a Mac menu bar app.
• Custom AI Rules: Define custom review patterns using AI prompts and regex to enforce team-specific standards.

• Faster Code Reviews: Stacked pull requests help teams break large changes into smaller reviews, making it easier for developers to get feedback and merge changes faster.
• Stay Unblocked: Start the next branch while previous PRs are still under review, keeping you in flow instead of context-switching.
• Strong CLI Ergonomics: The gt CLI is well-designed and uses standard Git primitives under the hood, so it plays nicely with existing tooling.
• Works Solo: You can adopt Graphite individually without requiring your whole team to switch tools.
• Developer-Friendly Workflow: Graphite’s CLI, VS Code extension, and Git-based tools simplify tasks like creating stacks, syncing changes, and managing pull requests.
• Modern Pull Request Experience: The PR interface brings code changes, reviews, status checks, and collaboration tools into a focused workspace designed for faster reviews.
• Better Pull Request Organization: The PR Inbox gives developers a central place to track review requests, pending changes, and team activity.

• Learning Curve: Stacked PRs and the CLI take time to learn, especially if your team isn't already comfortable with rebasing and trunk-based development.
• GitHub-Only: No support for GitLab, Bitbucket, or other Git hosts, which excludes many teams.
• Needs Team Buy-In for Full Value: The biggest gains from stacking require team-wide adoption and shared conventions, which can face resistance.
• AI Reviews Still Need Human Oversight: Graphite Agent can identify potential issues and suggest improvements, but developers still need to review recommendations, test changes, and handle final decisions.

• Breaking Down Large Features: Split a big feature like a checkout flow into small, dependent PRs (button, form, order processing) so each piece gets reviewed quickly instead of blocking on a 1,000-line PR.
• Trunk-Based Development at Scale: Teams practicing trunk-based development use Graphite to ship small changes continuously without waiting on review queues.
• Monorepo Development: Engineering teams working with large repositories can use Graphite to organize complex changes into smaller stacks, reduce review complexity, and manage dependencies between related pull requests.
• Automating PR Review Triage: Use Graphite Agent to catch bugs and style issues pre-merge so human reviewers can focus on architecture and logic.
• Managing Merge Conflicts Across Dependent Branches: When one PR in a stack needs changes, gt modify and gt sync handle recursive rebasing so you don't manually update every downstream branch.
• Tracking Engineering Productivity: Engineering leads use Insights to monitor review times, PR size, and cycle time to identify where developers get stuck.