AI agents write code fast. They also silently remove logic, change behavior, and introduce bugs -- without telling you. You often find out in production.
claude-lrc fixes this. It brings AI code review directly into Claude Code and reviews every diff before it lands. 60-second setup. Completely free.
Review, vouch, or skip β without switching tools or remembering separate CLI steps. Just tell Claude what you want, or use a slash command. Either way, the review runs.
claude-lrc1-final.mp4
- π€ AI agents write code fast and quietly. Logic removed. Behavior changed. Edge cases gone. You notice in production.
- π Review while the change is fresh. AI inline comments show you exactly what changed and what looks wrong β before it lands.
- π Review where the code was generated. You're already in Claude Code. The review stays there too.
- π£οΈ Natural language lowers friction. No separate CLI to remember. Just say what you want.
- π― Explicit commands give deterministic control. When you want exact behavior, slash commands deliver it.
- π Teams and individuals both benefit. The review habit is built in, not dependent on everyone remembering a step.
claude-lrc uses the LiveReview infrastructure for AI code review β the same backend that powers git-lrc.
You don't need git-lrc pre-installed. The plugin handles its own backend bootstrap during setup. But if you already use git-lrc, claude-lrc fits right alongside it β they share the same review state, git log entries, and coverage tracking.
π We also bundle git-lrc alongside this workflow. Use claude-lrc when you want review, vouch, skip, and hook control from natural language or slash commands inside Claude Code. Use git-lrc when you want git-native, editor-independent commit-time enforcement across repos and tools.
Add the marketplace:
claude plugin marketplace add HexmosTech/claude-lrcInstall the plugin:
claude plugin install lrc@claude-lrcReload plugins in the current Claude session:
/reload-pluginsRun setup directly:
/lrc:setup
Or just ask Claude:
set up lrc
Setup opens browser-based steps for:
- LiveReview account β sign in with Hexmos
- AI connector β connect a Gemini, OpenAI, Claude, or other supported API key
One-time setup. After this, review flows are ready in every repo you open in Claude Code.
Tell Claude what you want:
review with lrc
skip lrc review
vouch for this
check if lrc is active
enable lrc hooks
disable claude gate
The plugin routes those requests to the matching review or hook flow.
Use explicit slash commands when you want exact, predictable behavior:
/lrc:review
/lrc:skip
/lrc:vouch
/lrc:hooks
/lrc:setup
Stage your files, then ask for a review:
review with lrc
Or explicitly:
/lrc:review
The review UI opens in your browser. AI comments appear inline on the diff.
Intentionally bypass AI review and record that decision:
skip lrc review
Or:
/lrc:skip
The git log will record skipped β no review ran, and no attestation is made.
You've iterated, you're satisfied, and you want to take responsibility without triggering another AI pass:
vouch for this
Or:
/lrc:vouch
Coverage and iteration stats from prior review rounds are preserved.
check if lrc is active
enable lrc hooks
disable claude gate
Or use the explicit hook command:
/lrc:hooks
When a review runs, the UI opens in your browser. You get:
- GitHub-style diff β color-coded additions and deletions
- Inline AI comments β at the exact lines that matter, with severity badges
- Review summary β high-level overview of what the AI found
- Staged file list β all staged files, with navigation between them
- Copy issues β one click to copy all AI-flagged issues, ready to paste back into Claude
- Cycle through issues β navigate between comments without scrolling
Typical workflow with AI-generated code:
- Ask Claude to generate or modify code.
- Stage the files you want reviewed.
- Tell Claude
review with lrc. - Inspect the browser review β inline AI comments, summary, file list.
- Copy the flagged issues and feed them back to Claude to fix.
- Stage the fixes and run
review with lrcagain. - Repeat until satisfied.
- Use
vouch for thisor let Claude commit through the reviewed flow.
Each review with lrc is one iteration. The tool tracks how many iterations you did and what percentage of the final diff was AI-reviewed (coverage).
Every commit gets a review status line in the git log:
LiveReview Pre-Commit Check: ran (iter:3, coverage:85%)
LiveReview Pre-Commit Check: vouched (iter:2, coverage:50%)
LiveReview Pre-Commit Check: skipped
iterβ number of review cycles before committingcoverageβ percentage of the final diff that was AI-reviewed in prior iterations
This is shared with git-lrc. If you use both, you'll see a consistent review history across your git log regardless of which tool ran the review.
| Review | Vouch | Skip | |
|---|---|---|---|
| AI reviews the diff? | β Yes | β No | β No |
| Takes responsibility? | β Yes | β Yes, explicitly | |
| Tracks iterations? | β Yes | β Records prior coverage | β No |
| Git log message | ran (iter:N, coverage:X%) |
vouched (iter:N, coverage:X%) |
skipped |
| When to use | Each review cycle | Done iterating, ready to commit | Not reviewing this commit |
Review is the default. AI analyzes your staged diff and gives inline feedback.
Vouch means you're explicitly taking responsibility for this commit. Typically used after multiple review iterations β you've gone back and forth with Claude, fixed issues, and are now satisfied. No AI review runs, but your prior iteration and coverage stats are preserved.
Skip means you're not reviewing this particular commit. The git log records skipped.
| Input | What happens |
|---|---|
review with lrc or review this |
Review staged changes |
/lrc:review |
Review staged changes (explicit) |
skip lrc review |
Skip AI review, write attestation |
/lrc:skip |
Skip review (explicit) |
vouch for this |
Manual vouch without AI review |
/lrc:vouch |
Manual vouch (explicit) |
check if lrc is active |
Show hook status |
enable lrc hooks |
Enable hooks |
disable claude gate |
Disable Claude-surface hooks |
/lrc:hooks |
Hook management entry point |
/lrc:setup |
Interactive setup flow |
By default, setup connects Gemini (Google AI Studio). You can also connect:
- OpenAI
- Claude
- DeepSeek
- OpenRouter
To manage connectors, run:
lrc uiFrom the UI, you can:
- Re-authenticate your account
- Add or update AI connectors
- Reorder connectors to set priority
The first connector in the list is used for reviews.
- Discord: discord.gg/sGdnKwB3qq β quick questions, general Q&A, back-and-forth with the team
- GitHub Issues: github.com/HexmosTech/claude-lrc/issues β bugs and scoped feature requests
- git-lrc repo: github.com/HexmosTech/git-lrc β the CLI counterpart and shared backend
claude-lrc is distributed under a modified variant of the Sustainable Use License (SUL).
Note
What this means:
- β Source Available β Full source code is available for self-hosting
- β Business Use Allowed β Use claude-lrc for your internal business operations
- β Modifications Allowed β Customize for your own use
- β No Resale β Cannot be resold or offered as a competing service
- β No Redistribution β Cannot redistribute modified versions commercially
This license ensures the project remains sustainable while giving you full access to self-host and customize for your needs.
For detailed terms, examples of permitted and prohibited uses, and definitions, see the full LICENSE.md.
Using
claude-lrcsolo? Great. Building with a team? Check out LiveReview β the full suite for team-wide AI code review, with dashboards, org-level policies, and review analytics. Everythingclaude-lrcdoes, plus team coordination.
