Reviews & inline comments

Conversation summary

On each review, MergeGuard posts a top-level comment with risk score, severity breakdown, recommended fixes first, then per-file findings that could not be inlined.

Files changed (inline)

Findings anchored to diff lines appear as review comments on the Files changed tab. Reply on those threads for @mergeguards fix.

Test coverage

When source files change without matching test updates, MergeGuard posts a separate Missing test coverage comment after the review with a checkbox to use the agent to generate tests. See Test generation.

Triggers

• PR opened, reopened, ready for review
• New commits pushed (synchronize)—except MergeGuard auto-fix pushes
• @mergeguard-followup on the PR conversation

After auto-fix

MergeGuard does not run a full re-review on its own fix commits. Post @mergeguard-followup when you want another scan on the latest head.

When a review fails

If a review cannot finish (for example a GitHub API or network error), MergeGuard posts a short notice on the Conversation tab with a retry checkbox:

- [ ] 🔍 Trigger review

Check the box on that comment to run a full review again on the current PR head—no need to close the PR or paste @mergeguard-followup. A human user must click the checkbox (bots cannot trigger retry).

While the retry runs, the comment updates to show progress; on success it notes that the review completed.