MergeGuard Intelligence
Understand your codebase, PR risk, and engineering history before you merge.
MergeGuard Intelligence goes beyond diff-only review: system-wide context, merge-time warnings, and a persistent record of why code changed. Start with the Intelligence plan ($7/mo) for connected-repo Code Explorer; higher tiers unlock full system tracing and team-scale features. See also Code Explorer commands.
Full System Intelligence
Map how services and repositories connect—not just the files in one pull request.
- Cross-repository dependency graph
- Service-level impact analysis
- Architecture visualization
- Cross-service tracing
Plan availability
PR Intelligence Layer
Every pull request and merge request is analyzed before merge—not only when someone asks.
- Every PR auto-analyzed on open and update
- Risk scoring before merge (0–100 summary on each review)
- “What will break” warnings on high-blast-radius changes
- Suggested reviewers based on file history and past reviews
Reviews post on GitHub Conversation and GitLab MR overview. See How it works and GitHub reviews.
Engineering Memory
Persistent context so new teammates—and future you—know why a system looks the way it does.
- “Why was this added?” — purpose and decision hints from reviews and explore sessions
- “Who changed this system and why?” — author and change context
- PR decision history — outcomes, risk scores, and review summaries over time
- Persistent knowledge base — searchable from Dashboard → Engineering Memory
Open Dashboard → Engineering Memory on a connected workspace. Use /why-exists in Code Explorer for file-level history hints.
Risk Engine
Key feature. MergeGuard scores merge risk and surfaces blast radius before code ships.
- High-risk file detection — hot paths, auth, payments, infra
- Change blast radius — how many call sites and services are affected
- Breaking change prediction — API and contract drift signals on the diff
The risk score appears in every PR/MR summary. For deeper impact before editing, run /impact or /can-delete via Code Explorer.