Real PR · we run it on our own repo

This is what lands on your pull request

No mockups. Below is the kind of comment MermaidCreator posts when a PR changes your architecture, what it posts back when that PR merges and drift is detected — review-first, with the proposed update — and the PR where it stays silent because nothing meaningful changed.

mermaidcreator#48

Manage GitHub repo connections

app/api/github/installation/route.tsnewapp/api/github/repos/route.tsnewcomponents/workspace/github-panel.tsxmodifiedlib/github/app.tsmodified

MermaidCreatorbotcommented just now

🧭 Architecture impact

Medium risk

Adds workspace-level management for the GitHub connection: two new API endpoints let a workspace disconnect the app (removing its installation) and unlink an individual repo (stopping auto-sync while keeping the diagram). New teardown paths in the integration, so reviewers should confirm the data that's removed versus kept.

GitHub integrationAPI routesWorkspace settings

🔎 What this PR changes

Before

After

Why it commented:two new API endpoints and a new teardown path changed how the GitHub integration fits together — that's architecturally significant, so reviewers get the picture before reading the diff.

On merge · DiagramOps

Merge it, and the drift gets caught

When the PR lands on your main branch, DiagramOps checks the linked architecture diagram against the new code — and opens a review finding with a plain-English summary of exactly what moved and the proposed update. Nothing changes until you approve it, and no one has to remember to check the picture.

mermaidcreator#50Merged

Replace manual sync with automatic drift detection

MermaidCreatorbotcommented just now

Knowledge drift review

This merge changed your architecture. DiagramOps opened a review finding with the proposed diagram update — nothing changes until you approve it:

GitHub integration — architecture

Added: Merge to mainDrift detection
Removed: Manual sync
New connections: Merge to main → Drift detectionDrift detection → Linked diagram
Removed connections: GitHub webhook → Manual syncManual sync → Linked diagram

Review the finding — apply the patch in one click; the previous version stays in history.

Diagrams by MermaidCreator — keep your architecture diagrams alive in your repo.

And here's a PR where it says nothing

The best bot comment is often no comment. Silence is a feature — MermaidCreator never adds noise to a PR that doesn't change how the system fits together.

mermaidcreator#49

Fix README typo and bump eslint

README.md.eslintrc.jsonpackage-lock.json

No comment posted. Only docs, lockfiles and tooling config changed — nothing that affects the architecture. No AI spent, no notification, no noise.

Put this on your repo

Generate your first architecture diagram free, then connect a repo to get PR summaries like the one above. PR rendering and auto-sync are part of DiagramOps.

Try it on your repo See pricing