MergeGuard documentation
Help for GitHub, GitLab, and MergeGuardAgent — reviews, replies, and troubleshooting.
MergeGuard reviews the pull request or merge request where your team already works. With MergeGuardAgent, you can run the same review from your editor. Pick a platform below.
MergeGuardAgent — live on the Marketplace
mergeguardagent.mergeguardagent), sign in with your MergeGuard account, and run reviews from VS Code, Cursor, or Windsurf.New here?
Your first week
Day 1: connect. Day 3: apply a suggested fix. Day 7: a deeper pass.
Read more →GitHub quickstart
Install the app, open a pull request, and read your first review.
Read more →GitLab quickstart
Sign in with GitLab, connect a project, and review merge requests.
Read more →MergeGuardAgent
Install MergeGuardAgent, sign in, and review files or git diff from your editor.
Read more →MergeGuard Intelligence
System intelligence, PR risk, engineering memory, and the risk engine.
Read more →Code Explorer
Ask your codebase: explain flows, impact, root cause, and safe deletes.
Read more →Command reference
Follow-up, deep-scan, auto-fix, and test generation commands.
Read more →How it works
What MergeGuard posts on your PR or MR.
Read more →Test generation
Detect missing tests after review and commit AI-generated specs with one click.
Read more →Container image scan
Async Trivy CVE scan when a PR changes a Dockerfile (Pro+).
Read more →What you can do
- 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 fixon an inline thread to apply a suggested patch - Run
@mergeguard-followupor@mergeguards deep-scanwhen 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-testsor the Use agent to generate tests checkbox - MergeGuardAgent: review the current file, local
git diff, or lockfiles/IaC from your editor in your editor