The Cold Read A practitioner running roughly 200 pull requests a day has added a "cold" review agent that receives only the diff, with no PR description or prompt, and describes the change; a second judge agent then grades how well that description agrees with the original on an A-through-F scale. The cold read feeds the assessment deciding whether a PR can merge itself, so a description the diff does not back up counts against automerge; in one case it flagged a PR described as a performance enhancement whose memory cost had not been assessed. The author argues the approach works because the cold agent shares only the diff with the agent that wrote the code, making it an independent second view of the change. I give every PR to a separate agent "cold". It gets the diff alone, with no description and no prompt, and I ask it to describe the change. Then a second agent judges how well that description agrees with the original PR description, prompt, etc . A PR description is a claim