git-lrc

Hi @shrsv currently i've installed model in my local machine. can git-lrc use the models that installed via local machine ?

This is exactly what I needed. I've been using Cursor and Claude Code heavily, and honestly the scariest part isn't theAI writing bad code — it's me blindly accepting diffs without properly reviewing them. git-lrc sitting as a pre-commit hook forces me to actually look at what changed before it lands. The web UI with inline comments is a nice touch too, feels like doing a PR review on my own code. Already set it up on two repos.

What if want to run code review on PR because most of time my time goes on reviewing PR so I don't commit code. In that case I pull branch locally do some testing and review code. how it will helpful in this case ?

Good one! Congrats on the launch!! What's the typical token consumption per review, i know this might vary based on quantum of changes. But, would love to understand average cost of review. Thanks in advance and all the best !

I really like the idea. But what exactly does it check? Are there internal rules or standards?

This looks like a very interesting and timely tool for SWEs. Now that AI-generated code is becoming the norm, having a way to quickly pinpoint failures and streamline reviews is a huge time-saver. Great job on solving a modern pain point!

Congrats on the launch! I love the 'race car without brakes' analogy. Do you or will you support all kinds of linting standards?

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.Github: https://github.com/HexmosTech/git-lrcLanding Page: https://hexmos.com/livereview/git-lrc/