I really like the idea of treating review comments as feedback about the development process, not just the code. It’s easy to fix an issue, move on, and then completely forget about it until the same thing shows up in another PR.

The part about turning recurring findings into rules feels especially practical. Over time, the harness becomes a reflection of the actual mistakes the team encounters, rather than a collection of rules someone tried to predict upfront.

I also appreciate the reminder that not everything should be automated. The goal isn’t to remove humans from reviews, but to stop spending human attention on things that can already be checked consistently. That shift toward using reviews as a way to improve the system itself is a really interesting way to think about AI-assisted development.