MergeGuard documentation

Help for integrating MergeGuard on GitHub, GitLab, and MergeGuardAgent—reviews, commands, and troubleshooting.

MergeGuard reviews pull requests and merge requests where your team already works—and with MergeGuardAgent, you can run the same AI review from your editor. Choose your platform below for step-by-step help.

MergeGuardAgent — live on the Marketplace

Install from the Visual Studio Marketplace (mergeguardagent.mergeguardagent), sign in with your MergeGuard account, and run reviews from VS Code, Cursor, or Windsurf.

New here?

Most teams get their first review in a few minutes after connecting GitHub or GitLab.

Your first week

Day 1 install → day 3 first @mergeguards fix → day 7 deep-scan.

GitHub quickstart

Install the app, open a pull request, and read your first review.

GitLab quickstart

MergeGuardAgent

Install MergeGuardAgent, sign in, and review files or git diff from your editor.

MergeGuard Intelligence

System intelligence, PR risk, engineering memory, and the risk engine.

Code Explorer

Ask your codebase: explain flows, impact, root cause, and safe deletes.

Command reference

Follow-up, deep-scan, auto-fix, and test generation commands.

How it works

What MergeGuard posts on your PR or MR.

Test generation

Detect missing tests after review and commit AI-generated specs with one click.

Container image scan

Async Trivy CVE scan when a PR changes a Dockerfile (Pro+).

Automatic reviews when a PR/MR is opened or updated
Inline comments on changed lines
Risk score and recommended fixes in the summary
Reply @mergeguards fix on an inline thread to apply a suggested patch
Run @mergeguard-followup or @mergeguards deep-scan when you need another pass
Pro+: Dockerfile changes trigger an async container image CVE scan with a follow-up comment
Test generation: missing coverage callouts with @mergeguards generate-tests or the Use agent to generate tests checkbox
MergeGuardAgent: review the current file, local git diff, or lockfiles/IaC from your editor in your editor