Skip to main content

GitHub Copilot - Generate mermaid diagrams to better understand an existing codebase

Today I was reviewing an existing codebase and I had a hard time to get a good understanding about what was going on. I couldn't create a good mental picture in my head. But then I asked myself, maybe GitHub Copilot can help me out here and draw this picture for me. Let's give it a try...

Note: As we were using the Azure DevOps wiki, I decided to try to generate the visualization using Mermaid as this is supported directly in Azure DevOps.

Let me first shortly explain what Mermaid is before I dive into Copilot.

Introduction to Mermaid

Mermaid is a powerful JavaScript-based diagramming and charting tool that allows you to create and modify diagrams dynamically. It uses Markdown-inspired text definitions to render detailed diagrams and charts, making it easy to visualize complex information. Whether you're working on flowcharts, sequence diagrams, or Gantt charts, Mermaid has you covered.

Mermaid uses a simple syntax to define charts. Here is an example of a basic flowchart:

And this is how the rendered flowchart looks like:

 


Creating a Mermaid chart through Copilot

Ok, time for some action. Let’s see if and how Copilot can help us to navigate through this complex codebase. Our best friend here is the @workspace command. With this command you can ask Copilot Chat questions about your entire codebase. Based on the question, Copilot intelligently retrieves relevant files and symbols, which it then references in its answer as links and code examples.

A simple example:

 

Let’s now combine the power of the @workspace command with Mermaid and try to construct a prompt that returns us a good mermaid diagram. Here is the prompt I tried:

@workspace  Create a sequence diagram showing the data flow of the app. Please create this in mermaid format so that I can render this in a markdown file.

And this is the result I got back:

 

Nice!

Remark: I used the o1-preview model to generate the example above. I would recommend to certainly also try other models and compare the results.

More information

Markdown syntax for files, widgets, wikis - Azure DevOps | Microsoft Learn

Wiki Mermaid Diagrams - Azure DevOps.tips

Mermaid | Diagramming and charting tool

Chat using @workspace Context References

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...