GenAI is like a race car without brakes. It accelerates fast — you describe something, and large blocks of code appear instantly. But AI agents silently break things. They remove logic. Relax constraints. Introduce expensive cloud calls. Leak credentials. Change behavior without telling you. git-lrc is your braking system. It hooks into git commit and runs an AI review on every diff before it lands.

git-lrc started from a practical observation within my own team.

As our usage of AI coding tools like Copilot, Cursor, etc., increased, our velocity seemingly went up—but careful checking of the AI-generated code went down.

Engineers were committing code they hadn’t truly examined.

Reviews were happening later, sometimes too late, and often superficially (because AI generates tons of code)

This led to abstruse bugs and long debugging at prod.

Clearly, we needed a solution.

I didn’t want another dashboard. I wanted a strong nudge to review code at the right place—exactly where responsibility is bound to exist: git commit.

I prototyped git-lrc such that AI helps the developer work through diffs faster, acquire an understanding of what's going on, and fix issues on a commit-by-commit basis.

git-lrc was built with the idea that review shouldn’t be an afterthought. It should be structurally encouraged while putting the developer in control.

So in git-lrc, while a review is triggered automatically, the dev can still consciously skip the review.

Or they can manually review and "vouch" for the change they are making.

All these micro review decisions get recorded in git log—for future analysis so that the team could operate at higher engineering standards.

As to git-lrc, it takes 60 seconds to set up and is completely free for any number of reviews—thanks to Google Gemini's Free tier.

I encourage you to give git-lrc a try and see the difference in the quality of your code as well as concrete outcomes such as reduced production bugs.

git-lrc

About