technicaldiagrams.comv0.1 · visual references for agents
← Time & planning

Git branches

Follow commits and a merge across branches.

Visual 90/100Edit 85/100Balanced 88/100Editorial baseline · revision 1
Git branchesExplain one feature branch merging into main. All values are illustrative example data.A feature branch, mergedCommit order runs left to rightmainfeature/searchmerge
Live SVG · all content is illustrative

Make it yours

Edit labels & content

Change the text directly. Use the scene editor to move or add elements.

Edit individual elements

Choose a shape or text element, then change its properties. Related labels and connectors have separate coordinates.

Edit scene JSON

Change positions, dimensions, paths, and labels. Apply validates the scene before changing the preview. Primitive reference ↗

Review this diagram

Your scores and review history stay in this browser. Export reviews to propose a catalog update. Read the rubric.

    Use this when

    Explain one feature branch merging into main.

    Choose another form when

    The history contains many branches or a complex rebase.

    Built from

    TrackMarkerConnectorLabel

    Two tracks keep history legible; extra merges need custom routing.

    Initial editorial assessment by Codex · 2026-09-07. Scores are judgments about this example, not a benchmark of AI capability.

    Give your agent this reference

    Use the example to show your agent the form you want. Describe your system or provide your source material, then ask it to generate an adapted diagram and inspect the result.

    Includes the reference URL, current scene, and settings. Paste it into your own agent.

    Read the agent workflow ↗

    Take the source

    The SVG is self-contained. The JSON preserves editable primitives and your presentation settings. Labels remain text; shapes remain vectors.

    Original scene JSON ↗
    Controls, limits, and embedding ↗