Skip to main content
Glama

repopilot_review_change

Destructive

Review a Git change locally to identify weakened tests, CI gates, and security boundaries. Returns a JSON report with findings, blast radius, and confidence-tiered signals.

Instructions

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 base (e.g. "origin/main") to review a branch. For a repository health check that is not about one change, use repopilot_scan instead. Returns a JSON report with a decision, findings on changed lines vs the rest, blast radius (files that import the changed files), and deterministic signals grouped by confidence tier (definitely / maybe / noise) in tiered_signals: checks the change weakened (focused or skipped tests, removed tests, tests that lost assertions, new lint/type/coverage suppressions, relaxed CI or tool gates); security-boundary changes (auth, CORS, CI, dependency manifests, committed .env); behavioral changes (network, subprocess, filesystem, env, dependency, migration, or raw SQL added; error handling, an auth check, or a test removed; a removed named TypeScript/JavaScript export that a resolved local caller still imports); algorithmic changes (deeper nesting, a new nested loop, a grown function, new recursion); and taint-lite reachability (HTTP request or process arguments reaching SQL, exec, filesystem-write, or outbound-network sinks in a changed function). Signals are evidence, not verdicts; explain one with repopilot_explain_review_signal. RepoPilot uploads nothing. Only a non-empty verify array runs commands: the configured local checks, which may modify workspace files or contact external systems. Their captured output is bounded and redacted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoBase Git ref to diff against, e.g. "origin/main". Optional; defaults to the working tree vs HEAD.
headNoHead Git ref. Optional and only valid together with "base".
pathNoRepository path to review. Defaults to the current working directory.
limitNoMaximum findings to return.
scopeNo"changed" reports findings in the changed files only; "full" also returns findings from the rest of the repository.changed
configNoOptional repopilot.toml path. Defaults to the one discovered in the repository.
detailNo"compact" returns at most 20 findings and 20 signals; "full" returns all of them.compact
intentNoOptional inline statement of what the change is meant to touch (paths, contract families, critical paths, verification IDs). The report marks drift outside it. It is metadata only and cannot execute commands.
offsetNoZero-based finding offset.
verifyNoIDs of checks configured in repopilot.toml to run on the reviewed revision. They run as local processes. Omit to run nothing.
filtersNoOptional thresholds and rule IDs that narrow the returned findings.
profileNo"default" hides low-signal suggestions; "strict" shows all findings.default
baselineNoOptional baseline file (from `repopilot baseline create`). Findings recorded in it count as accepted debt, separate from new findings.
intent_pathNoOptional repository-rooted TOML file that states what the change is meant to touch. The report marks drift outside it. Use either this or `intent`, not both.
fail_on_reviewNo"definitely" fails the report's gate when a gate-eligible definitely-tier signal is present; "none" reports signals without gating.none

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.24.2
    • changedInput schema / properties / baseline / description
      Previous value: -"Optional baseline path."New value: +"Optional baseline file (from `repopilot baseline create`). Findings recorded in it count as accepted debt, separate from new findings."
    • changedInput schema / properties / config / description
      Previous value: -"Optional repopilot.toml path."New value: +"Optional repopilot.toml path. Defaults to the one discovered in the repository."
    • addedInput schema / properties / detail / description
      Added value: +"\"compact\" returns at most 20 findings and 20 signals; \"full\" returns all of them."
    • addedInput schema / properties / fail_on_review / description
      Added value: +"\"definitely\" fails the report's gate when a gate-eligible definitely-tier signal is present; \"none\" reports signals without gating."
    • addedInput schema / properties / filters / description
      Added value: +"Optional thresholds and rule IDs that narrow the returned findings."
    • changedInput schema / properties / intent / description
      Previous value: -"Optional bounded intent data. It is metadata only and cannot execute commands."New value: +"Optional inline statement of what the change is meant to touch (paths, contract families, critical paths, verification IDs). The report marks drift outside it. It is metadata only and cannot execute commands."
    • changedInput schema / properties / intent_path / description
      Previous value: -"Optional repository-rooted bounded TOML intent file."New value: +"Optional repository-rooted TOML file that states what the change is meant to touch. The report marks drift outside it. Use either this or `intent`, not both."
    • addedInput schema / properties / profile / description
      Added value: +"\"default\" hides low-signal suggestions; \"strict\" shows all findings."
    • addedInput schema / properties / scope / description
      Added value: +"\"changed\" reports findings in the changed files only; \"full\" also returns findings from the rest of the repository."
    • changedInput schema / properties / verify / description
      Previous value: -"Configured local verification check IDs to run explicitly."New value: +"IDs of checks configured in repopilot.toml to run on the reviewed revision. They run as local processes. Omit to run nothing."
  2. First observedv0.24.1

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond annotations: signals are evidence not verdicts, RepoPilot uploads nothing, only a non-empty verify array runs commands, those commands may modify workspace files or contact external systems, and output is bounded and redacted. This aligns with and enriches destructiveHint=true and openWorldHint=true without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, usage, and alternative routing, then details return structure and safety constraints. It is long because the tool is complex, and most sentences earn their place, though the single dense sentence enumerating signal categories is harder to scan than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 15-parameter schema, output schema, nested intent/filters objects, and destructive/open-world annotations, the description is complete. It covers usage, safety, side effects, return shape, tiered signals, and the explain-sibling for signal details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds useful semantic framing for key parameters: base defaults to working tree vs HEAD, verify IDs run configured local checks, and intent is metadata-only and cannot execute commands. This is meaningful beyond the schema for high-impact fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: review a Git change locally, covering what it touched and which checks it weakened. It explicitly distinguishes itself from repopilot_scan for repository health checks, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit timing guidance (before finishing work or a merge), default behavior (uncommitted work vs HEAD), how to review a branch (pass base), and names the alternative for non-change health checks. When/when-not/alternative are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.