Hello, I'm Shrijith. I'm building git-lrc, an AI code reviewer that runs on every commit. It is free, unlimited, and source-available on Github. Star Us to help devs discover the project. Do give it a try and share your feedback for improving the product.
In this series, I am on a journey to build for myself DBChat - a simple tool for using AI chat to explore and evolve databases.
See previous posts to get more context:
Building DBChat - Explore and Evolve Your DB with Simple Chat (Part 1)
Making DBChat VSCode Extension - Ping Pong With LSP Backend (Part 6)
Manage TOML Configuration From VSCode Extension - DBChat Part 8
Getting DBChat Working For the First Time In VSCode - Part 9
A Video Demo (Step Up from Screenshots Last Time)
You can see me do a bunch of things in the following demo:
See existing DB connections
See various operations (show DB creds, edit, delete)
Chat with a specific DB
Generate SQL options from simple English prompt
Execute SQL and show results
Refine the SQL with more specific/pointed English prompt
What's New
Fixed various annoyances with the chat window: Enter key not working, scrollbar resetting on response, etc
Earlier DB credentials were exposed in the listing page; now there's a specific eye icon - which must be clicked to show any sensitive information
I have a better testing setup now - with custom database, users, and so on. Will speed up development from now on due to the foundation.
Bugs and things learned
With LLMs - I tried doing a bit of "vibe coding" that Karpathy talked about.
It is important to commit/snapshot things as we vibe code, so that we can revert to working state if things go wrong.
LLMs get into loops and do the same errors again and again, and sometimes never seem to learn/improve. I have to jump in and fix things often.
Had a pretty table come up once, but it was a hardcoded HTMLfrom the LSP. So tried to dynamize it - for almost an hour. See above - the LLM went into an unproductive broken code loop. Had to set this challenge for another day.
Found a bug with "Edit Connection". Maybe LLM interfered with my old code, but now, on clicking save, a new connection was created rather than updating old one.
The "Show DB credentials" feature is not working reliably
The "Add Connection" method via connection string is quite unfriendly. I want to give an LLM interface to add DBs. So you could paste pretty much anything, and it'll collect the necessary information.
*AI agents write code fast. They also silently remove logic, change behavior, and introduce bugs -- without telling you. You often find out in production.
git-lrc fixes this. It hooks into git commit and reviews every diff before it lands. 60-second setup. Completely free.*
Any feedback or contributors are welcome! It's online, source-available, and ready for anyone to use.
⭐ Star it on GitHub:
HexmosTech
/
git-lrc
Free, Unlimited AI Code Reviews That Run on Commit
git-lrc
Free, Unlimited AI Code Reviews That Run on Commit
AI agents write code fast. They also silently remove logic, change behavior, and introduce bugs -- without telling you. You often find out in production.
git-lrc fixes this. It hooks into git commit and reviews every diff before it lands. 60-second setup. Completely free.
See It In Action
See git-lrc catch serious security issues such as leaked credentials, expensive cloud operations, and sensitive material in log statements
git-lrc-intro-60s.mp4
Why
- 🤖 AI agents silently break things. Code removed. Logic changed. Edge cases gone. You won't notice until production.
- 🔍 Catch it before it ships. AI-powered inline comments show you exactly what changed and what looks wrong.
- 🔁 Build a habit, ship better code. Regular review → fewer bugs → more robust code → better results in your team.
- 🔗 Why git? Git is universal. Every editor, every IDE, every AI…
Top comments (1)
This looks great.