Pull Requests

Diagrams in pull requests

Add architecture diagrams to your PRs. Architecture diffs alongside code diffs — review, comment, and merge structural changes with full context.

Why diagrams belong in PRs

Architecture changes should ship with the code that implements them.

Visual diffs in PRs

Diagram changes appear as text diffs. See new services, removed links, and renamed components at a glance.

Mermaid renders on GitHub

GitHub and GitLab render Mermaid in Markdown preview. See the actual diagram alongside the diff.

Inline comments

Comment directly on diagram lines: "Should this service call the cache or the DB?" Same UX as code review.

Architecture + code together

Architecture changes ship in the same PR as the code change. One review, one merge, one record.

AI-generated updates

Describe the change in English. Cybewave updates the Mermaid or PlantUML code for you.

CODEOWNERS for diagrams

Require architect approval for diagram files. Same CODEOWNERS rules you already use for critical paths.

Add diagrams to your next PR

Free to start. 50 AI credits/month. No credit card required.

Get started for free →