How the Claude Code team thinks about verification
The Claude Code team describes verification loops for agent-written changes: run the actual application, use end-to-end, property and differential tests, and escalate persistent failures to a human.
Their review rules come from the base branch rather than the change being judged; they evaluate reviewers against past incidents and clean changes. The article also says unresolved flaky tests may be deleted with an explanation—a consequential policy worth scrutinizing.
Hacker News commenters debated the cost and reliability of agent-driven checks versus reusable deterministic tests; others argued the two can catch different failures.