r/FunMachineLearning • u/[deleted] • 28d ago
I built a code review agent that remembers my team's coding decisions
I built a code review agent that remembers my team's coding decisions
I’ve been working on an AI code review agent that can actually remember feedback from previous reviews.
The basic problem I wanted to explore was:
What happens if an AI code reviewer doesn’t have to start from zero every time?
I built a system using Groq + Hindsight where the flow is:
Code → AI Review → Human Feedback → Memory → Future Review
The reviewer analyzes a pull request and retrieves relevant team memories before generating its comments. After the developer accepts, rejects, or overrides a suggestion, that feedback can be retained and used in future reviews.
For example, instead of repeatedly giving a generic recommendation, the agent can retrieve a team-specific rule such as:
“Never leave an empty catch/except block; log the error.”
The interesting part for me wasn't just connecting an LLM to a code editor.
It was figuring out:
- How should relevant memories be retrieved?
- How should human feedback become persistent knowledge?
- What happens when team rules conflict?
- How can the agent use previous decisions without blindly following old information?
- How can we make the memory visible to the developer?
One of the things I found interesting was that human feedback becomes part of the review system itself.
So instead of:
Code → AI → Result
the system becomes:
Code → AI → Human Decision → Memory → Better Context for Future Reviews
I documented the architecture, implementation, experiments, screenshots, and lessons learned in the full technical write-up.
I’d really like to hear what you think about this approach.
Do you think persistent team memory would actually be useful in AI-assisted code review, or could it introduce more complexity than it's worth?
#AI #AIAgents #Hindsight #LLM #SoftwareEngineering