Local-First Code Reviewer

Why I built it

PR-only review tools provide feedback after code has already been pushed and assembled into a pull request. I wanted a shorter feedback loop: review the change while it is still staged locally and easy to revise.

Workflow

The tool starts with the staged Git diff rather than sending an entire repository. It can obtain surrounding context selectively when a focused review needs more information.

Product decisions

The current direction separates correctness review from security review and uses a cheaper security triage step before deciding whether more expensive analysis is warranted.

• Diff-first analysis to keep reviews focused.
• Less unnecessary source-code exposure and token usage.
• Selective context gathering rather than whole-repository submission.
• Correctness and security treated as different review concerns.

Current state

The project currently includes a Go CLI and VS Code integration. It is new, in active iteration, and its workflow is changing based on actual use.

How it is being built

The implementation has been developed heavily with AI-assisted workflows. The problem framing and several product decisions are mine, while substantial architecture and implementation details were proposed or produced with AI assistance.

What I am learning

The project is helping me evaluate product tradeoffs around context, cost, privacy, and review timing while also building practical exposure to Go and extension development.