Know when your architecture diagram no longer matches the code

Link a shape on your canvas to the files or folders it describes. When a pull request that touches those files merges, the shape gets a badge, shapes downstream by arrow are outlined, and one click files a review note. Open pull requests that will touch the files show a heads-up before they merge.

What you get

Per-file, not per-repo

A shape is flagged only when a merged pull request touched the files it is linked to, so alerts stay rare and believable.

Heads-up before the merge

Open pull requests that will change a linked shape show a separate badge, so reviewers see the diagram impact first.

Blast radius

Shapes downstream by arrow get a dashed outline, so you can see what else the change may affect.

Fix it in one review

Suggest update adds a review note listing the pull requests and files, in the same tray as other suggestions.

How it works

  1. 1Connect GitHub to your Co-Space and add the repository card.
  2. 2Link a shape to the files or folders it describes.
  3. 3Watch for the badge, review the note, then mark the shape up to date.

Questions

Does it rewrite my diagram automatically?

No. It points to what changed and lets you decide. A wrong automatic edit is worse than a pointer.

What does it need from GitHub?

Pull request metadata and the list of changed file names. It does not keep file contents or diffs.

Which diagrams does it cover?

Any shape on the canvas can be linked to repository paths.

Plan software visually. Ship it from GitHub.

Open a canvas in seconds. No account, no credit card.