Analyze a file for code review findings. Only flags risk on lines changed vs the git baseline (diff-aware). Pass content to analyze unsaved or generated code before it is written to disk. When a code graph is available, public-surface findings carry an impact field (caller count, suggested reviewers, test gaps) and may be tier-adjusted — fix high-blast-radius findings before surfacing the code.

Check all staged (or working-tree) changes in a git repo for DiffGate findings. Returns overall tier, counts, and per-file findings across the whole diff, plus a verdict block (the agent autonomy ladder: pass/review/blocked overall, with a rung — block/escalate/autofix/advisory — per finding) so you can decide whether to surface the diff without reimplementing the rules.

Run an agentic deep review on a single high-impact (orange) finding. The model uses real repo tools (grep, read_file, find_references, git_blame) to investigate blast radius before rendering a verdict.

Get a concise AI explanation for a DiffGate finding. Faster than diffgate_deep_review — a single LLM call with no tool loops.

Report which DiffGate layers are active (core / code graph / LLM), which tools you can call right now without an error, and the agent autonomy budget (fix limit, escalation, trust source). Call this once up front so you know what's available instead of discovering it via thrown errors.

Review the diff against the repo's own coding guideline files (AGENTS.md, CLAUDE.md, .cursorrules, etc.), scoped per directory (nearest file wins). IMPORTANT: if the result has mode='host', NO external model was used — this is a SELF-REVIEW, not an independent gate: YOU (the calling agent) evaluate each group's hunks against its guidelines text using your own model. Treat host-mode results as ADVISORY only — never block the change on them. If mode='model', findings were produced by the configured provider and are returned directly.

Record a reviewer's verdict on a finding so DiffGate learns. verdict 'dismiss' suppresses that same flagged code (ruleId + code) in future reviews (noise reduction); 'confirm' marks it as a real, valued catch. Stored in .diffgate/learnings.json at the repo root.