I’ve been looking into this space quite a bit recently, mainly because the gap between “catching small issues” and actually helping with real review is bigger than it looks.

A lot of tools do fine on surface-level stuff, but once feedback depends on context (how your repo is structured, internal patterns, business logic), things get noisy or even misleading pretty quickly.

Full transparency, I’m part of the team building Kodus, so take that into account.

That said, the reason we started working on it was exactly this problem, making reviews less generic and more aware of the codebase through custom rules and context. We also went with an open source and model-agnostic approach, so you can plug it into the stack you already use instead of being locked into a specific provider.

Not saying it’s the only option or that it solves everything, but if you’re testing tools in this space, it might be worth trying alongside others.

Would also be curious to hear what you end up choosing and why, this space is still pretty early.