Code Flowchart Generator

When to Use It

When reviewing complex code or writing technical docs, describing execution paths, module dependencies, and data movement in prose can be hard to scan. This skill turns code context into flowcharts, which helps with code review, architecture notes, onboarding, and interface tracing. It is aimed at code logic visualization rather than generic drawing, producing Mermaid, ASCII, HTML, image, or PDF outputs.

How It Works

You provide code context, functional description, target chart type, detail level, and preferred output. The skill identifies what to express: an execution flowchart, component diagram, system architecture diagram, data flow diagram, decision tree, tree structure, or a grouped process with subflows. Then it organizes nodes into start/end, process, decision, input/output, subflow, and connecting lines. It also supports direction such as TD or LR, color themes, node shapes, spacing, borders, font size, and annotations. For hierarchy-heavy structures, subgroups or tree layouts can keep related nodes together and reduce crossing lines.

Limits and Notes

It works best for medium-complexity modules with clear structure. For large systems, split the explanation into execution flow, data flow, and architecture-level views instead of forcing one oversized diagram. If code depends heavily on runtime state, implicit callbacks, distributed concurrency, or complex condition combinations, the flowchart can only cover main paths and should be read with the source code. Prioritize readability first, then add detail.