sequence-diagram

To generate a sequence diagram, run this skill on your repository to automatically extract call relationships and output a ready-to-render D2 file. It traces interactions across packages and files from entry points to create a visual flow.

Visualizing runtime call sequences is best handled by generating a D2 sequence diagram that maps function interactions across modules. This approach derives relationships directly from code structure to aid onboarding and debugging.

Yes, you need D2 installed to render the sequence diagrams generated by this skill. The tool outputs a self-contained .d2 file named <flow-name>-sequence-diagram.d2 to your specified output directory for rendering.

Static analysis traces entry points and interactions by examining the code structure to identify function call relationships across packages and files. It uses this derived flow data to build a clear sequence diagram output.

Yes, you can use sequence diagrams for debugging complex code call interactions by visualizing the runtime sequence of calls across structs and modules. This helps engineers reason about startup and interaction flows.

Limitations of D2 diagrams for code flow visualization include requiring a local D2 installation to render outputs. The tool analyzes static code structure to derive call relationships, meaning dynamic runtime behaviors might not be fully captured.