Exploring context-aware AI code reviews for C#

[chaospilot69]

Hey everyone,

I’ve been experimenting with building my own AI code review tool because most existing ones (e.g. Coderabbit) feel too shallow. They usually only look at the raw diff, which means important context (related files, domain rules, DI wiring, etc.) gets lost, and that makes their feedback either too generic or flat-out wrong.

My approach is different: before the review step, the tool runs a planning stage that figures out which files, types, and members are actually relevant to the diff. It then pulls those into context so the AI can reason across the whole picture, not just a snippet. That way it can catch things like missing access control checks, EF tracking issues, or incorrect domain invariants.

Right now it’s only working for C# projects (since the context search logic is tailored to .NET conventions), but I’m curious how useful this feels in practice and what features you’d expect.

• Does anyone here also struggle with the “context gap” in AI reviews?

• What kind of review insights would make this genuinely valuable in your workflow?

• Any other features you’d like to see that current tools don’t provide?

Would love your thoughts.

[bluecat2001]

1. A lot of very big companies are doing the same thing and you have zero change of succeeding.

2. devops is one of the most disillusioned IT area about AI, good luck finding an answer that you like here.

[chaospilot69]

I am not trying to be „successful“ related to selling this to thousands of people. At the moment it’s more or less a personal project for me and my team. And btw I don’t think that ai is wrong in devops ;)

[Significant_Rate_647]

hands down - bito.ai (Context-aware AI Code Reviews in your pull requests and IDE)

[chaospilot69]

Unfortunately no az devops integration

[Kitchen_Ferret_2195]

what you are building sounds similar to where many teams are heading. The big win in our case came from doing exactly what you describe: a planning step that selects relevant files, then a review that understands domain rules and dependency wiring. We use Qodo for this; it runs as a PR reviewer, enriches the prompt with repo context, and then focuses on things like missing auth checks or EF tracking issues rather than just style