{"author":"atomicnature","children":[],"created_at":"2026-06-16T14:04:05.000Z","created_at_i":1781618645,"id":48555511,"options":[],"parent_id":null,"points":9,"story_id":48555511,"text":"Hi HN, I&#x27;m the author of git-lrc, would appreciate some feedback from the community<p>Last year my team started using AI coding tools more heavily, and we found ourselves generating tons of code, but spending less time looking at the stuff that&#x27;s been generated.<p>We felt like we were losing a bit of grip&#x2F;understanding of what we were building. Regressions occasionally slipped through. Sometimes changes made it all the way to production only to be reverted later.<p>We tried several AI code review tools, but most operate at PR time. That felt too late. I wanted review to happen while the implementation was still fresh in the developer&#x27;s mind at a team level (soft enforcement). I also wanted to emphasize responsibility for keeping prod stable with each individual engineer.<p>So I built git-lrc.<p>When you commit, git-lrc opens a review UI with your diff. It summarizes what changed, points out things that deserve a second look, and lets you quickly jump through the important parts of the change.<p>Over time, git-lrc has grown to check for around 100 common risk patterns across 10 categories, including security, reliability, performance, maintainability, etc.<p>Note that this is far from a formal review. It&#x27;s a quick 60 seconds spent looking at your own work before it gets recorded in git.<p>It also generates a short &quot;summary deck&quot; that highlights the main changes, with special emphasis on potential risks. With git-lrc you can quickly sanity-check what you&#x27;re about to ship and obtain greater confidence in what&#x27;s been generated.<p>In my mind it is less of an AI reviewer and more as a habit for AI-assisted development: a small pause to make sure we understand and stand behind the code we&#x27;re shipping.<p>Developers can review the change, vouch for it, or consciously skip the review. Those decisions get recorded in git history, creating a  trail of how code was reviewed before it shipped.<p>It&#x27;d be great if you could take a look, give it a try in your projects or teams and let me know what you think.<p>Happy to take feedback from the HN community and improve it over time!<p>GitHub: <a href=\"https:&#x2F;&#x2F;github.com&#x2F;HexmosTech&#x2F;git-lrc\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;HexmosTech&#x2F;git-lrc</a>","title":"Show HN: git-lrc \u2013 Free, Micro AI Code Reviews That Run on Git Commit","type":"story","url":"https://github.com/HexmosTech/git-lrc"}
