I always want to like tools in this vein, but I typically find myself disappointed. And I've spent too many hours trying to use diagrams to make sense of code, of systems, of workflows, etc. But I think the problem is there's a goldilocks zone where diagrams etc are the right tool.

If the thing you're making sense of is small, a diagram doesn't add much value and may not be needed.

If the thing you're making sense of is too large or complex, a diagram may not be sufficient; you'll likely need to introduce new simplifying groupings or abstractions, or else the diagram will be a huge sprawling tangle. And the diagram may not be even a good start in helping you to identify what those abstractions or groupings should be.

In graph terms, you want the number of nodes to be moderate, and you want the maximum degree of any node to be relatively low. The graph doesn't need to be planar but it helps if it is. And even if you can draw out your diagram and make sense of it today, as your system/repo/whatever grows in complexity, will it still be diagrammable in six months?