Giant AI PRs? Here's How Meta Engineers Do It
In this video, Tomas (co-founder of Graphite) does a live demo from scratch showing exactly how stacked diffs work. Breaking down those massive PRs into small, reviewable chunks that you can actually read. This is a real workflow from Meta/Google engineers, not a toy example. Testing if it actually solves AI code review fatigue. ⚠️ FULL DISCLOSURE: Graphite sponsored this video and is giving everyone 2 months of their team plan for free (no credit card needed). Use code STACKWITHRAY at https://rfer.me/graphite SUPPORT THE CHANNEL Join 200+ builders in our private Discord where we ship AI apps together: https://rfer.me/discord This stream is powered by Ray Transcribes. Get professional, AI-powered transcripts for your content. https://raytranscribes.com Wispr Flow (Voice to Text): https://rfer.me/wispr WHAT YOU'LL ACTUALLY SEE: - Live demo from Graphite co-founder Tomas (completely raw, no editing) - How to visualize branch dependencies with 'gt log' - Creating a 4-PR stack from a single feature (OpenAPI spec → Server → Frontend → Icons) - Submitting entire stacks to GitHub as linked PRs - Modifying a PR in the middle of the stack without rebase hell - How 'gt modify' automatically updates dependent branches - Viewing detailed change history (V1 vs V2) in Graphite UI - Real merge conflict handling THE GRAPHITE CLI COMMANDS: - `gt log` - Visualize your stack as a graph - `gt log short` - Condensed stack view - `gt create` - Create new branch on top of stack - `gt submit` - Submit entire stack as separate PRs - `gt modify` - Update a PR and auto-rebase dependents - `gt up` - Move up the stack - `gt continue` - Resume after merge conflicts KEY TIMESTAMPS 00:00 - The Problem with AI-Generated Code 01:22 - Visualizing Branch Dependencies (gt log) 02:34 - Stack Logic: API Spec → Server → Frontend 04:20 - Live Demo: Creating a New Branch in the Stack 05:40 - Submitting the Stack to GitHub (Multiple PRs) 06:58 - Modifying a PR Mid-Stack (gt modify) 09:05 - Viewing Change History in Graphite UI 10:06 - Free Graphite Team Plan + Recap THE WORKFLOW TOMAS SHOWED: 1. Create branches for each logical chunk of your feature 2. Each branch builds on the previous one (dependencies) 3. Use `gt submit` to open all PRs at once 4. Review each small PR independently (easier to catch bugs) 5. If changes needed mid-stack, use `gt modify` to auto-rebase 6. Merge from bottom up (base → dependent → top) WHY THIS MATTERS FOR AI CODING: AI agents generate tons of code fast. That's great for velocity, but terrible for code review. No one actually reviews a 500-line PR properly. Stacked diffs let you: - Break AI changes into reviewable pieces - Keep coding without waiting for reviews - Catch bugs in isolated changes - Avoid massive rebase nightmares - Ship faster with better quality GET YOUR FREE GRAPHITE TEAM PLAN: 2 months free with code STACKWITHRAY ✅ Unlimited AI code reviews ✅ Graphite CLI access ✅ Web dashboard for stack management ✅ No credit card needed Link: https://rfer.me/graphite THE ADOPTION PLAN: This is the workflow I'm introducing into my AI coding projects in 2026. If you're building with AI agents and drowning in massive PRs, try this. Drop a comment with your biggest Git headache. CONNECT WITH RAY X (Twitter): https://x.com/RayFernando1337 Weekly AI Insider Newsletter: https://dub.sh/RayMasterAI ABOUT THE HOST Ray Fernando is a former Apple engineer with 12+ years of experience, testing AI tools against production reality. Currently shipping apps live from Hawaii while maintaining honest, practitioner-focused content about AI coding workflows. #StackedDiffs #Graphite #CodeReview #AIcoding #GitWorkflow #ProductionCode #PullRequests #RayFernando #DeveloperTools #CodeQuality
