RepoPilot MCP server

RepoPilot

Local, deterministic review for Git changes.

RepoPilot helps developers and teams inspect a change before merge. It reports structural evidence about security boundaries, behavior, local imports and exports, and the files affected through the dependency graph. The same review can run from a terminal, in CI, or through an agent integration.

The analysis runs on the machine or CI runner that invokes it. It does not send source to a hosted service or call an embedded language model. Findings point to code and explain what to check; reviewers still decide whether a change is safe for their application.

Example: a change that weakens its own tests

This change drops a range check from applyDiscount. The same change skips the test that would now fail, removes an assertion from another test, and lets the CI test step fail without failing the job. Every check that still runs passes. repopilot review . lists them right after its decision:

Decision: REVIEW (Change Proof: REVIEW)
...
Checks this change weakened (details under Review signals):
  ⚑ check gate relaxed — .github/workflows/ci.yml:10
  ⚑ assertions removed — src/pricing.test.ts:5
  ⚑ test skipped — src/pricing.test.ts:9

Further down, each signal explains itself:

⚑ check gate relaxed — .github/workflows/ci.yml:10  check step `npm test` in job `test` now has `continue-on-error: true`
    ⚑ assertions removed — src/pricing.test.ts:5  "applyDiscount > takes a percentage off the total": assertions 2 → 1
    ⚑ test skipped — src/pricing.test.ts:9  `it.skip` added on "rejects a discount above 100%"; its result no longer fails the run

These are excerpts of one run (recording). Replay it with scripts/demo-weakened-tests.sh , then run repopilot review .

Install and review

cargo install repopilot
# or
npm install -g repopilot

repopilot review . --base origin/main

For uncommitted work, run repopilot review .. The first screen gives one PASS, REVIEW, BLOCK, or NOT ASSESSED decision, its reasons, coverage limits, and a next action.

A review can surface:

configuration;

• changes to authentication, request trust, deployment, dependencies, or secret

writes, SQL, or error handling;

• added or removed behavior such as network calls, subprocesses, filesystem

contracts;

• changed input-to-sink paths, algorithmic structure, or local import/export

it.only, newly skipped tests (it.skip, @pytest.mark.skip, t.Skip, #[ignore]), removed or substituted test cases, tests that lost assertions, new lint, type, or coverage suppressions, and relaxed CI or tool gates (continue-on-error, || true, lowered coverage thresholds, strict mode off), so a green run cannot hide them;

• tests the change stopped running or weakened: committed focus markers such as

• direct dependents and the wider impact of changed files.

Signals are advisory evidence. For example, a taint-lite signal shows that a recognized input can reach a recognized sink in the changed source. Confirm the impact in the context of the application and its configured checks.

Example: review an image-processing change

The Wagtail example removes an authorization check and passes request data to a subprocess in a one-file change. RepoPilot reports both the boundary change and the input-to-process flow.

Shortened. The full README is on GitHub.