Understand the change
See beyond the patch.
Start with the real diff, then surface impact and provenance where they change what deserves attention. Untouched callers and dependents stay connected to the code you are reviewing.
LemonCrow Review
Understand what your coding agents changed — and why.
Review the real diff with impact outside the patch, provenance, and recorded verification evidence — while keeping the decisions and assumptions made during agent work as durable engineering history. That context survives the session and carries forward across revisions alongside human review state.
Actual product demolc review --open
Real demo repository · revision-pinned Diff, Preview, Compare, Markdown, API, and review-state surfaces.Reproduce demo →
Review updates
Pick up where you left off.
When a new revision arrives, LemonCrow shows what changed since your last review. Files you already reviewed stay marked; updated and new files come back into focus.
Reviewed
Unchanged files stay done.
Needs review
Updated files return to your queue.
New
New files are added automatically.
Comment threads stay with the code when they still match. If a line moved too much, LemonCrow marks the thread as outdated instead of silently attaching it somewhere else.
Since your last review3 files
src/auth.tsReviewed
src/router.tsNeeds review
src/billing.tsNew
Show only files that need another look.
What Review adds
Review the change with the context that matters.
Keep the reasoning
Don’t let the agent session be the only record.
Decisions, assumptions, and supporting evidence made while the agent works stay with the Review instead of disappearing when the session ends. Later agents and reviewers can see why the implementation exists.
Trust the evidence
Recorded checks stay evidence, not an AI verdict.
Verification results are shown when LemonCrow has them. Missing execution evidence stays unknown rather than being turned into a synthetic green badge.
Keep your judgment
Review state survives the next revision.
Unchanged reviewed work can stay reviewed. Changed work reopens. Comments re-anchor only when the new location is unambiguous, and grounded feedback can go back to the agent.
What stays attached to the work
Impact
Trace changed definitions to callers, dependents, and untouched sites outside the patch.
Decisions
Keep important implementation choices as durable Review history instead of leaving them trapped in one agent session.
Assumptions
Carry forward the facts an implementation relies on so later revisions can make those dependencies visible again.
Provenance
Show which agent work produced the record when that evidence exists; leave provenance unknown when it does not.
Verification
Surface recorded checks and execution evidence without turning missing evidence into a pass.
Review state
Bind human judgment to reviewed content so unchanged work can stay reviewed after revision.
Comments
Move anchors only when the new location is unambiguous; otherwise orphan instead of guessing.
Feedback
Export grounded review objections back to the agent for the next revision.
Human judgment stays final
AI can narrow the work. You make the judgment.
changed → reread
unchanged reviewed → preserve
missing evidence → unknown
final judgment → human
Start locally
Your agent finished. Now review the work.
$ curl -fsSL https://lemoncrow.com/install.sh | bash
$ cd your-project && lc init
$ lc review --openLocal use requires no LemonCrow account. Review state and source analysis stay on your machine.