Command reference
Commands you can post on pull requests and merge requests.
| Command | What it does | GitHub | GitLab |
|---|---|---|---|
/explain-flow | Map how data and control flow through a file or module | PR · Dashboard · VS Code | MR · Dashboard · VS Code |
/root-cause | Trace why a bug, error, or behavior happens | PR · Dashboard · VS Code | MR · Dashboard · VS Code |
/impact | Blast radius if you change or remove code | PR · Dashboard · VS Code | MR · Dashboard · VS Code |
@mergeguard-followup | Runs a full re-review on the latest code | PR Conversation | MR Overview note |
@mergeguards deep-scan | Deeper security-focused review (paid plans) | PR Conversation | MR Overview note |
@mergeguards fix | Applies an AI-generated fix commit | Reply on inline review comment | Reply on Changes diff thread |
@mergeguards generate-tests | Commits AI-generated or extended test specs for coverage gaps | Review summary or PR Conversation | Review summary or MR Overview |
Code Explorer
Six commands for understanding existing code — see the full guide at Code Explorer.
Aliases
You can also use @mergeguard, /mergeguards, or /mg for deep-scan, fix, and generate-tests. Follow-up should be posted as @mergeguard-followup on its own line.
Tips
- Post the command on its own line for best results.
- Fix only works on MergeGuard inline finding threads—not general PR/MR chat.
- After an auto-fix or test generation, run
@mergeguard-followupif you want another full review. @mergeguards generate-testsworks from the Use agent to generate tests checkbox or MR/PR conversation — see Test generation.- If a review fails, check 🔍 Trigger review on the MergeGuard failure comment on the PR Conversation tab to retry (human users only). See GitHub troubleshooting.