repopilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
RepoPilot reviews Git changes and repositories locally and deterministically. It calls no model and uploads nothing. Pick a tool by the question:
What did this change touch, and which checks did it weaken? repopilot_review_change (uncommitted work by default; pass
base, e.g. "origin/main", for a branch).What needs attention in this repository or folder overall? repopilot_scan.
What should I know before editing this codebase? repopilot_context.
Why was this finding reported? repopilot_explain_finding with its
finding_id, after a scan or review.Why was this review signal raised? repopilot_explain_review_signal with its
signal_id, after a review.How does RepoPilot treat this file, and which rules apply to it? repopilot_explain_file. Findings and signals are evidence, not verdicts: confirm the impact in the code. Treat
behavioral.quiet-fallback-introducedas a candidate path, not proof of harm, and preserve intentional recovery behavior. Re-run a review after editing; stored results describe the workspace at the time of the call.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repopilot_review_changeA | Review a Git change locally: what it touched and which checks it weakened. Use it before finishing work or before a merge. By default it reviews uncommitted work (working tree vs HEAD); pass |
| repopilot_scanA | Audit a repository, folder, or file for findings across architecture, coupling, code quality, security, and testing, and return the JSON scan report (findings, metrics, risk summary). Use it for a health check that is not about one change. To review what a change touched or which checks it weakened, use repopilot_review_change; for a short Markdown brief to read before editing, use repopilot_context. Explain a returned finding with repopilot_explain_finding. Runs entirely on disk; nothing is uploaded. |
| repopilot_contextA | Generate a budgeted Markdown brief of the repository (risks, hotspots, structure) to read before editing, especially in an unfamiliar codebase. Use it for orientation. For the full findings as JSON, use repopilot_scan; to review a change, use repopilot_review_change. Pass |
| repopilot_explain_fileA | Explain how RepoPilot treats one file: the role it assigns (for example test, generated, config, or CLI command handler) and the evidence for it, which rules apply, the ordered overrides that change a rule's severity, and whether the default profile would show the result. Use it to understand a file without a report, or to ask why a rule ( |
| repopilot_explain_findingA | Explain why a finding was reported. Use it when you have a |
| repopilot_explain_review_signalA | Explain one signal from a review: where it came from, its confidence tier, whether it can fail a gate, the files it affects, how to verify it, and its limits. Use it after repopilot_review_change, with a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-change | Review the current change with RepoPilot evidence. |
| fix-top-risk | Plan the smallest fix for the highest-priority RepoPilot risk. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| RepoPilot rule catalog | |
| RepoPilot repository summary | |
| Available RepoPilot analysis handles |
TDQS
Scored across 6 tools
The three top-level entry points are clearly distinct: repopilot_scan (health audit as JSON), repopilot_review_change (diff review), and repopilot_context (Markdown brief), and each description explicitly says when to prefer the others. The only soft spot is the trio of explanation tools, whose names (explain_finding vs explain_review_signal vs explain_file) are similar and whose correct choice depends on knowing whether you hold a finding_id, a signal_id, or a path — the descriptions do call this out, so misselection is unlikely but not impossible.
All six tools share a repopilot_ prefix and snake_case with a clear verb_ or verb_noun shape (review_change, explain_finding, scan). The only deviation is repopilot_context, which uses a bare noun rather than a verb, breaking the otherwise predictable pattern slightly. Still highly readable and consistent overall.
Six tools is well-scoped for a local repo audit/review server: three do the work (scan, review_change, context) and three provide explanation for the objects those produce. No tool looks like filler, and nothing essential appears to be collapsed into an overloaded god-tool.
The read/analyze/explain lifecycle is covered thoroughly: audit, change review, orientation brief, and explanation for findings, signals, and files. Minor gaps remain — there is no tool to inspect or manage configuration profiles/suppressions or to enumerate available rules/detectors in bulk, which an agent doing suppression cleanup would want. For a read-only analysis server, core workflows are not blocked.