git-lrc

// What it does

• Global commit hook: every git commit is reviewed automatically, or run git lrc review by hand, with --vouch to take personal responsibility or --skip to bypass
• Browser review UI with a GitHub-style diff, inline AI comments with severity, a summary, per-file diff stats, one-click issue copying and a Commit / Commit & Push / Skip decision
• Issue Navigator that filters findings by severity, type and risk category, with thumbs up/down feedback and Send to Claude, plus an auto-generated summary slide deck for each review
• Risk-scored review view that ranks hunks by blast radius and review priority from a local codebase-memory-mcp knowledge graph, with the contributing signals shown for every score

• Review status written into git log (iterations and coverage), an --agent-mode for coding agents and CI that returns JSON, and a bundled claude-lrc slash-command workflow for Claude Code
• Per-repository rules and ignore patterns in a version-controlled .lrc/ directory, plus bring-your-own-key connectors for Gemini, OpenAI, Claude, DeepSeek, OpenRouter and Atlas Cloud

// Getting started

git-lrc installs as a single binary and sets up its hooks globally. You need a Hexmos (LiveReview) sign-in and, by default, a free Gemini API key from Google AI Studio. The commands below come from the project README.

# Linux/macOS via IPM
curl -L https://hexmos.com/ipm-install | bash && ipm i HexmosTech/git-lrc

# or the direct install script
curl -fsSL https://hexmos.com/lrc-install.sh | bash

git lrc setup

git add .
git lrc review          # run AI review first
# git lrc review --vouch   # vouch personally, skip AI
# git lrc review --skip    # skip review entirely
git commit -m "add payment validation"

git add .
git lrc review --agent-mode
git commit -m "add payment validation"

lrc config init
lrc config check
lrc config preview

lrc ui
git lrc hooks disable   # disable for current repo
git lrc hooks enable    # re-enable later

Commands and code are distilled from the project's own documentation — always check the official repo for the latest.

// When to use it

• Reach for it when AI coding agents write much of your code and you want every diff checked for removed logic, leaked secrets or costly calls before it enters git history
• Reach for it when your team uses different editors and assistants and you want one review checkpoint that does not depend on an IDE extension
• Reach for it when you want git log to record which commits were AI-reviewed, vouched for or skipped, and how much of each diff was covered
• Reach for it when a large diff needs triage and you want its hunks ranked by blast radius so the riskiest changes are read first

// How git-lrc compares

git-lrc alongside other open-source ai code review & security tools AI/TLDR tracks, ranked by GitHub stars.