> Then you look at the code. Code that has passed review, generally. You realize that the database schema has been broken silently, and that the agent has rewri

> Then you look at the code. Code that has passed review, generally. You realize that the database schema has been broken silently, and that the agent has rewritten the tests or the golden fixtures to match. I find that the code review leg of this is critical to invest a lot of energy into hardening. First is don't trust the code review from your local harness, even if it uses sub-agents; externalize it into another system. Second is to get your most critical human code reviewers to encode their heuristics in markdown files and feed those to the code review agents. Third, if possible, is to bring the code review "into the loop" so that it's not only running in the PR, but also running in the coding loop so the coding agent has immediate, external feedback. Final PR code review is a backstop. This pattern [0] works well because it solves for some team level problems where folks are using different harnesses or different models (consistency issues) and it means that code reviews don't just sit at the end of the loop; it actively alters the code production cycle. [0] https://zeeq.ai/docs/key-features/code-review-tool https://zeeq.ai/docs/key-features/code-review-tool