Skip to content
AppArch AppArch Docs

ArchPilot - PR/MR comment bot

ArchPilot leaves inline architecture comments whenever a pull/merge request is opened - telling you exactly what is wrong, why, and how to fix it.

Highlights

Section titled “Highlights”
  • Diff-focused analysis - only the code that changed in that PR/MR is reviewed; old debt does not turn into noise.
  • Deduplicated & auto-resolving - comments are keyed by a marker; the same finding is not rewritten on every push, and fixed violations close automatically.
  • Assigned bot account + comment language - comments come from the default integration user or from a workspace-specific bot account; you choose the comment language per workspace.
  • Optional manual review - manually trigger a specific MR from the panel.
  • Project/workspace rule override - turn rules on or off per project or workspace.

How it works

Section titled “How it works”
  1. A PR/MR is opened → ArchPilot catches the event.
  2. The changed code is scanned in your own CI pipeline, against your rule set.
  3. The finding is written on the relevant line with its rationale and suggested fix.

The AppArch section in the description

Section titled “The AppArch section in the description”

Alongside the inline notes, ArchPilot keeps one report on the merge request itself - an AppArch section at the end of the MR description: files scanned, lines analyzed, the severity breakdown, what this push resolved (file, line, rule) and what is still open (each line links to its inline thread). The section sits between two hidden markers, so every run rewrites that block in place and never touches the text the author wrote above it.

If the credential can comment but cannot edit the merge request, the same report is posted as a summary comment instead (and a summary comment left by an earlier version keeps being updated).

  • The numbers are diff-scoped, not repo-wide. Quoting repo totals would tell the author of a clean MR that they have 24 problems.
  • The score is computed from the same scope: what this merge request itself introduced.
  • The footer carries the branch and the collector version. A stale runner tag silently skips every rule shipped since - and its clean verdict looks identical to any other.
  • The summary honours your ArchPilot comment-language setting.

Resolve with AI

Section titled “Resolve with AI”

When the installation’s operator has set up an AI provider and switched on Allow fix suggestions on findings, a Resolve with AI button appears under each finding in the panel and produces a fix suggestion. There is no per-workspace key. See the AI integration page for setup, what is sent and how answers are stored.