惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
SecWiki News
SecWiki News
WordPress大学
WordPress大学
小众软件
小众软件
博客园 - 司徒正美
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
Y
Y Combinator Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
云风的 BLOG
云风的 BLOG
MyScale Blog
MyScale Blog
K
Kaspersky official blog
T
The Exploit Database - CXSecurity.com
腾讯CDC
Scott Helme
Scott Helme
I
InfoQ
Cyberwarzone
Cyberwarzone
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Security Latest
Security Latest
The Register - Security
The Register - Security
Project Zero
Project Zero
F
Fortinet All Blogs
C
CERT Recently Published Vulnerability Notes
A
Arctic Wolf
C
Cisco Blogs
L
LINUX DO - 热门话题
P
Privacy International News Feed
IT之家
IT之家
U
Unit 42
P
Privacy & Cybersecurity Law Blog
H
Help Net Security
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
C
Cyber Attacks, Cyber Crime and Cyber Security
P
Palo Alto Networks Blog
F
Full Disclosure
宝玉的分享
宝玉的分享
Simon Willison's Weblog
Simon Willison's Weblog
L
Lohrmann on Cybersecurity
Google DeepMind News
Google DeepMind News
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
H
Hacker News: Front Page
Know Your Adversary
Know Your Adversary
PCI Perspectives
PCI Perspectives
Hugging Face - Blog
Hugging Face - Blog
AWS News Blog
AWS News Blog
MongoDB | Blog
MongoDB | Blog
S
Schneier on Security
Recent Announcements
Recent Announcements
Forbes - Security
Forbes - Security
Cisco Talos Blog
Cisco Talos Blog

Graphite blog

Introducing Code Tours: a new way to review Introducing Cursor Cloud Agents in Graphite Building the future of software development with Cursor Reimagining the PR Page: Designing for speed and focus Graphite changelog [11-20-2025] Graphite changelog [11-04-2025] Graphite changelog [10-16-2025] The future of engineering is collaborative (and already here) Meet Graphite Agent: the next evolution of AI code review Introducing frozen branches: A safer way to build on your teammates’ work Graphite changelog [09-17-2025] How we sped up code search for Graphite Chat Introducing Graphite Chat How I got Claude to write code I could actually ship How we built the first stack-aware merge queue (and why it matters) How we organize our monorepo to ship fast Graphite brings stacking to Tower Code review tooling: Should you build or buy? Making AI code review available to everyone Introducing: The new Graphite + Linear integration Graphite raises $52M and launches Diamond to reimagine code review for the age of AI Why AI will never replace human code review How stacked PRs unblock distributed development teams Graphite is going to Developer Week 2025 Beating the end of year code freeze How Graphite’s eng team ships code remarkably fast Why we chose Anthropic's Claude to power Graphite Reviewer AI code generation will remain fragmented How we redesigned Graphite's landing page in-house Introducing Graphite Reviewer: your AI code review companion How AI code review reduces review cycles to improve developer productivity What if you could get instant feedback on your code? The new developer toolchain Not Rocket Science - How Bors and Google’s TAP inspired modern merge queues Graphite's State of code review 2024 How Google migrated billions of lines of code from Perforce to Piper Going from 0 to 1: How to write better unit tests when there are none Speed up your merges: Parallel CI is now generally available for teams using Graphite’s merge queue Down for less than four minutes a month: how AWS deploys code BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days Graphite is now free for startups and open source projects Launch week wrap-up (May 2024) Reduce CI costs for Buildkite and GitHub Actions Cheaper CI & faster merging with batching How Google does code review The technical learning curve at a startup is gentler than you might think Graphite will now automatically rebase your partially-merged stacks Multiple engineers can now seamlessly collaborate on the same stack of PRs Do you ever outgrow GitHub? From the 80's to 2024 - how CI tests were invented and optimized Graphite changelog [4/10/2024] 🎺 Graphite changelog [4/25/2024] 🐸 How Stack Overflow replaced Experts Exchange How GitHub monopolized code hosting Graphite changelog [3/27/2024] 🤝 The core principles of building a good AI feature Onboarding roulette: deleting our employee accounts daily Graphite changelog [3/13/2024] 🚁 Why Facebook doesn’t use Git How to recreate the Phabricator code review workflow Types of code reviews: Improve performance, velocity, and quality What's the best GitHub pull request merge strategy? Phabricator vs GitHub vs Graphite: How do they stack up? Improving team velocity through better pull request practices Moving fast breaks things: the importance of a staging environment Building trust as a software engineer Keeping code simple: moving fast by avoiding over-engineering What's better than GitHub pull request filters? The Graphite pull request inbox 7 Best Phabricator alternatives for PR stacking + code review [2024] Accurate eng estimations: predicting and negotiating the future Tracking and understanding GitHub PR stats: A step-by-step guide 8 pull request best practices for optimal engineering What’s next for Graphite Graphite Q1 Launch week: Stacking with the tools you love Graphite Q1 Launch week: Making stacking seamless Accelerating code review The Mom Test How to use stacked PRs to unblock your entire team Graphite Q1 launch week 2024 The practical and philosophical problems with AI code review Empirically sup code review best practices Call site attribution: how to pinpoint rogue SQL queries throttling your performance Every engineer should understand git reflog Post mortem: we took 124 seconds from you, here's 378 back Your GitHub pull request workflow is slowing everyone down Optimizing CI/CD workflows for trunk-based development Why we use AWS instead of Vercel to host our Next.js app How large pull requests slow down development 3 key lessons in application server optimization Trunk-based development: why you should stop using feature branches Git was built in 5 days Why large companies and fast-moving startups are banning merge commits How long should your CI take? Experimenting with AI code review CRA to AppRouter in 5 Steps: A case study with Graphite Graphite Changelog [10/18/2023] The comprehensive guide to writing the best PR title of all time How 10,000 Developers All Contribute to the same Repo
AI is writing code—here's why it also needs to review that code
Sara Verdi · 2025-07-29 · via Graphite blog

AI coding tools are causing a seismic shift in the way software is written. Developers are no longer writing software line-by-line; instead, they’re using large language models (LLMs) to generate everything from small edits to entire files in seconds. This faster, AI-powered iteration loop, sometimes referred to as “vibe coding,” can boost productivity, but it also introduces new risks: logic bugs, security gaps, and technical debt can creep in if engineers don’t review and understand the generated code.

The solution isn’t to slow down or stop using AI. Instead, teams need better ways to review AI-generated code. In fact, tools like Graphite are helping teams turn vibe coding into something more robust: responsible AI-assisted development, where code is still written quickly, but passes through high-quality, human-in-the-loop feedback cycles before it ships. In this post, we’ll explore the challenges of reviewing AI-generated code and show how AI tools can help teams keep quality high, even as output scales.

What is vibe coding?

Vibe coding is a new development technique where devs rely heavily on AI to generate code, often without fully understanding the entire scope of what the model produces. Rather than writing every line of code themselves, devs work more intuitively—they go off of the “vibes.”

However, just because you are using AI in the development process doesn’t necessarily mean you are vibe coding. Plenty of teams use AI to write code faster—but as one developer puts it, “When I talk about vibe coding I mean building software with an LLM without reviewing the code it writes.” This approach can be great for rapid prototyping, but generating production code with vibes alone introduces a host of new challenges for developers in the rest of the software development lifecycle (SDLC). 

The challenges vibe coding creates

As more code is written, it puts more  pressure on the “outer loop” of the development cycle.  Reviewing, testing, and merging quickly become the bottleneck to shipping faster.

With the sheer volume of potentially unchecked vibe code entering the outer loop, teams face issues that today’s manual code review workflows weren't designed to handle, such as: 

  • Review bottlenecks: Reviews take longer when code is unfamiliar or AI-generated because devs have to spend extra time understanding logic they didn't write.

  • Exponential complexity: Teams of ten now face challenges of scale that previously would have been faced by a team of 100 due to the volume of output. 

  • Knowledge gaps: Developers may not fully understand the code they're shipping, making it harder to debug issues or modify functionality later.

  • Technical debt accumulation: AI-generated code might work but could be inefficient, poorly structured, or use outdated patterns that create long-term maintenance problems.

  • Testing blind spots: Teams might not know what edge cases to test for since they didn't think through all the implementation details themselves.

This leads to an interesting question: If we’re increasingly using AI for generating code, can AI help ease the burden of reviewing all that code?

Reviewing AI-generated code with AI

In practice, introducing AI to the code review process isn’t just an effective solution—it’s quickly becoming a necessity for creating high-quality software with AI. Without pairing AI code generation tools  with an equally powerful AI reviewer, teams risk technical debt spiraling out of control. Fortunately, AI code reviewers can now analyze each pull request in seconds catching everything a human reviewer would notice—and more. For instance, Graphite Agent, Graphite’s AI code review companion, can automatically detect and flag:

  • Subtle logic errors.

  • Security vulnerabilities.

  • Performance issues.

  • Code style or quality issues specific to your org.

Graphite Agent scans your PRs and provides you with instant, actionable feedback that you can commit with a single click. 

In fact, 30-35% of all actionable code review comments at organizations using Graphite Agent come from the AI tool. This is huge for vibe coding teams who need a first layer of quality control on AI-generated code—and now human reviewers can spend more of their time thinking through  high-level functionality and architecture decisions rather than hunting for bugs in code they didn't write. Adopting AI in the code review process leads to better code, faster iterations, and ultimately, higher-quality software that keeps both your teams and end users happy.

Steps for standing up AI powered reviews within your teams

Choose an AI review tool
Chances are, if your teams are vibe coding, you’re already comfortable with them using AI-powered tools. Now, it becomes a question of which tool makes sense for your team. Prioritize looking for features like seamless integration with your current tools (GitHub, GitLab, etc.), customization capabilities, and actionable feedback features. For example, Graphite Agent's AI reviews allow teams to define custom rules aligned with their internal coding standards, so teams can enforce specific practices such as avoiding certain patterns or enforcing naming conventions.

Establish clear roles
It’s important to define the roles of AI versus human reviewers for efficiency in your review process. AI tools excel at automated checks, catching syntax errors, enforcing style consistency, and identifying security vulnerabilities or performance issues. Meanwhile, human reviewers can focus on broader architectural decisions, contextual business requirements, and creative problem-solving. A clear workflow could be: AI initially reviews code, developers incorporate that feedback, and human reviewers then address high-level concerns. This way, you can leverage the strengths of both AI and your development team.

Monitor, measure, adapt
To effectively implement AI code reviews, you need to monitor and adapt your processes based on actionable metrics. Graphite Agent provides insights into your team's productivity gains from AI code review, including the number of pull requests reviewed, issues identified, and the rate at which AI-suggested changes are accepted or dismissed. By analyzing this data, teams can assess Graphite Agent's effectiveness, identify areas for improvement, and make informed decisions on how to adapt their review processes.

Keep reviews on pace with AI code generation

As AI continues to accelerate software development, implementing an AI/human hybrid code review process  is essential to keeping your code correct, performant, and secure. Don’t fall behind the wave; get started with Graphite Agent to make sure your teams maintain speed and innovation without sacrificing quality or incurring technical debt. If you're curious about how our engineers are approaching AI-powered development and reviews, check out this article, too.