Claude Code 团队如何用 Claude 做代码评审
Quoting Addy Osmani, Morgan Westlee Lunt, and Qing Wang
Claude Code 团队自己怎么用 Claude 审代码，评审前置成拼写检查式的持续流程，写代码的都该看看
Addy Osmani、Morgan Westlee Lunt 和 Qing Wang 介绍了 Claude Code 团队的代码评审实践。他们提出"是否有人读过代码"是粗糙的代理指标，更该问的是"这个改动可能出什么问题，该由自动化还是人来检查"。评审从 PR 末端的关卡变为类似拼写检查的持续过程，多数改动在被人工查看前已由 Claude 至少评审并修复一次。这能拦截大部分常规错误，让团队把注意力留给更高层面的问题。
Quoting Addy Osmani, Morgan Westlee Lunt, and Qing Wang
We think "did a human read the code?" is an imprecise proxy for "what could go wrong with this change, and which check—automated or human—is the right one to catch it?" Asking that question also changed when review happens. Before, review was a gate at the end of the road: write the code, open a PR, wait for your colleague. Now, review runs continuously, more like spellcheck while you write. Most changes have been reviewed and fixed by Claude at least once before a human is asked to look. This catches most routine mistakes, and saves team attention for higher-level questions and scrutiny. — Addy Osmani, Morgan Westlee Lunt, and Qing Wang , How the Claude Code team does code review Tags: anthropic , claude , ai , claude-code , llms , addy-osmani , coding-agents , generative-ai , agentic-engineering , code-review
