How the Claude Code team does code review

Re:How the Claude Code team does code review by walthamstow on Friday October 16, 2026 @04:52PM (#50124506)

Using a different lab's model to review the code to the one that wrote it. Claude model plans/codes, OpenAI model reviews, or vice versa, or DeepSeek or GLM or whatever.

[ Parent | on HN ]

Re:How the Claude Code team does code review by a3nz3g on Friday October 16, 2026 @07:41PM (#50126270)

I do it this way too. I think having the same lab's model review the code in a fresh session also helps, so I use both: I generally start a new Claude Code and a Codex and have them review the code with a focus on 3 things: 1. bugs, 2. cut corners, 3. code style.

This generally works for me. I think a solid spec is the key for the models to review against. I ask them to follow the spec, and if the spec doesn't say, follow first principles.

Also, if there is a user experience change, they need to notify me.

How about your pattern?

[ Parent | on HN ]

Re:How the Claude Code team does code review by eivindmeyer on Monday October 19, 2026 @02:15PM (#50155871)

We had some nice results showing that this actually helps (it has been our intution for a long time, but nice to show it!)

https://theopenengine.com/blog/review-loop/

[ Parent | on HN ]