review-local-changesLABSCO SUMMARY
Reviews the working tree, not the pull request.
The scope is deliberately narrow: uncommitted changes in the repository the server was launched from, which makes it a pre-commit reader rather than a PR bot. Two things follow from that. The working directory matters — start it somewhere else and it reviews someone else's diff — and the quality of the judgement is Gemini's, since this server's job is to assemble the diff and the lint output and hand them over.
What it is
A code-review server that works on local, uncommitted changes. It gathers the git diff, runs static analysis, hands the combined context to the Gemini CLI, and returns a structured JSON review rather than prose — so findings arrive with a file, a line and a severity attached.
What you get
- A single tool,
review-local-changes, that finds every modified or added.js,.ts,.tsxand.vuefile throughgit diffand reviews them together - Static analysis without configuring it: the server falls back between ESLint, JSHint and the TypeScript compiler, picking the best one available in the project
- A JSON result with
summary,assessmentand afindingsarray — each finding carryingfilePath,lineNumber,severity,category,commentandsuggestion - A clear no-op when nothing relevant changed: the tool answers "No relevant files changed" instead of inventing a review
Requirements
Node.js 18 or later, npm, and Git, since the diff is collected from your working tree. You also need the Google Gemini CLI (gemini) installed and authenticated — the review itself runs there. It is not installed from npm — the code-review-mcp-server package there is a different project — so clone the repository, run npm install and npm run build, then point your client at dist/index.js with node. Launch it from the repository root you want reviewed, because the server reads the git workspace it is started in.
Setup effort
Build from source — git clone https://github.com/shaunie2fly/ndlovu-code-reviewer.git
USE CASES
01
Reading your own diff before committing
Call the review tool from the repository root and get findings pinned to file and line, with a suggestion attached to each, while the changes are still cheap to alter.
02
Getting lint results and a code review in one pass
Let the server pick the linter the project already supports and fold those findings into the same structured response as the review comments.
03
Feeding review findings into another step
Take the JSON findings array — file, line, severity, category, suggestion — and drive a fix loop or a checklist from it instead of parsing prose.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Node.js 18 or later
- Git
- Gemini CLI (gemini) installed and authenticated
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/shaunie2fly/ndlovu-code-reviewer.git
cd ndlovu-code-reviewer
npm install
npm run buildMCP Clients
Claude Code — VS Code extension
CLAUDE CODE — VS CODE EXTENSION · JSON
{
"mcpServers": {
"ndlovu-code-reviewer": {
"command": "node",
"args": [
"<YOUR_PATH_TO_NDLOVU_CODE_REVIEWER>/dist/index.js"
],
"cwd": "<YOUR_PATH_TO_NDLOVU_CODE_REVIEWER>"
}
}
}The server reviews the git changes of the folder it starts in, so set cwd to the root of the repository you want reviewed; only the path in args points at your ndlovu-code-reviewer clone. Left as written, it reviews the reviewer's own checkout.
Gemini CLI
GEMINI CLI · TERMINAL
gemini mcp add ndlovu-code-reviewer node $(pwd)/dist/index.jsRoo Code
Open Roo Code and click the server icon at the top of the Roo panel.
Choose Add MCP Server → STDIO and enter Name ndlovu-code-reviewer, Command node, Arguments <YOUR_PATH_TO_NDLOVU_CODE_REVIEWER>/dist/index.js, and Working Directory — the root of the repository you want reviewed.
Save the configuration and enable the server for your workspace. Roo stores it in either the global mcp_settings.json or the project .roo/mcp.json file.
The review covers the git changes of the working directory, so that is the project you want reviewed; only Arguments points at your ndlovu-code-reviewer clone.
Codex
CODEX · TERMINAL
codex mcp add ndlovu-code-reviewer node $(pwd)/dist/index.js
