“Just review the code” sounds simple, but it breaks down in real organizations. At my last job, every pull request was supposed to get two reviews. Most teams had one mobile engineer, so those reviews often came from engineers on other teams who had very little context for the code. The process was technically satisfied, but two approvals were not the same as informed verification. It gets worse when one person is managing agents across ten repositories. No human can keep every contract, dependency boundary, canonical pattern, and prior decision in working memory. Code review might catch a bad line. It does not standardize how five engineers decompose problems, structure services, reuse existing code, or decide which architectural pattern is authoritative. Without a common process, you get duplicated logic and a sprawl of competing architectures. Agents amplify that problem because every engineer also uses AI differently. The problem I am trying to fix is not a lack of review. It is the lack of a shared process that turns team decisions into contracts, validators, and evidence the whole system follows. Human review remains necessary, but it cannot be the entire operating model.

We have some enterprise restrictions, so we can't use cloud agents like github cloud or cursor-bot and all. So built a reviewer agent of my own using the GitHub Copilot SDK. It used multiple subagents with various expertise and custom skill subsets. Asked the team to do a self-review before raising the PR using the tool. this let it handle some concerns or convention issues related to our codebase. also allows us to push custom rules with just an update to tool. After that its moved to reviewers like me, where I usually check it out. And then run an agent and then try asking questions and do some specific probing like how is this working, let rewrite this like this with this structure, would that help or is there a challenge, so almost like refactoring on the way. and then, once, i am satsified i ask the agent to comment on the tool. I also wrote a skill for making the comments in my tone and phrasing. Once the pr comes back, I go take a look at it manually, because there are still things ik agent, won't catch. One of the things i look for is reduce LOC/simplify. The models really love complicating stuff. Just last week, i stopped a PR which was trying to push 2000+ stuff into the monolith, which could have been just simple DI.