The Agent Finished. The Reviewer Is Still Reading.
Generating a patch and understanding its consequences consume different resources. I want agent workflows to respect the capacity of the people reviewing them.
7 min read
The Agent Was Right. The Scope Still Changed.
An AI agent made a sound improvement, and I agreed. A colleague found his task implemented in my PR. What should review verify beyond the quality of the code?
9 min read
Who Checks the Tests an AI Agent Writes?
An AI agent can write code and tests that agree on the same mistake. I want the expected result to come from somewhere other than the implementation under test.
8 min read
A Review Belongs to a Commit
Review automation has to track more than whether it has seen a PR. Findings, CI evidence, duplicate suppression and guarded actions need a revision and a lifecycle, while final approval remains an accountable human decision.
7 min read
AI Code Review Should Sound Like a Careful Engineer
I built a personal AI reviewer for GitHub Pull Requests, not as a cold rule bot, but as a local and observable tool that checks known risk patterns and turns them into useful engineering conversation.
8 min read