Code To Diagram

CommunityPopular

zebbern

code-to-diagram

Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a module diagram from source code.

Overview

Publisher	zebbern
Repository	`claude-code-guide`
Skill name	`code-to-diagram`
Stars	4.6K
Forks	464
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by zebbern on GitHub. Read the source before you install it.

Installation

Install the Code To Diagram AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/zebbern/claude-code-guide.git /tmp/claude-code-guide
mkdir -p .claude/skills
cp -r /tmp/claude-code-guide/skills/code-to-diagram .claude/skills/code-to-diagram

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Code To Diagram in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Code To Diagram on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Code To Diagram is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Code to Diagram

Extract import and dependency relationships from a codebase via AST parsing, and automatically generate three types of diagrams:

Architecture Diagram — Module/directory-level dependency relationships
Flowchart — File-level import call chains
Org Chart — Directory/file hierarchy structure

Supported languages: Python, JavaScript, TypeScript, Go, Java

Output formats: Mermaid text (.mmd) or SVG images (requires mmdc installed on the system)

Usage

Basic: Analyze an Entire Project

bash
python3 scripts/analyze_codebase.py /path/to/project

Outputs three Mermaid diagrams to stdout and writes .mmd files to the current directory.

Specify Diagram Type

bash
# Architecture diagram only
python3 scripts/analyze_codebase.py /path/to/project --type architecture

# Flowchart only
python3 scripts/analyze_codebase.py /path/to/project --type flowchart

# Org chart only
python3 scripts/analyze_codebase.py /path/to/project --type org

Specify Output Directory and Format

bash
# Output to a specific directory
python3 scripts/analyze_codebase.py /path/to/project --output /tmp/diagrams

# Output as SVG (requires mmdc)
python3 scripts/analyze_codebase.py /path/to/project --format svg

# Output both Mermaid and SVG
python3 scripts/analyze_codebase.py /path/to/project --format both

Output JSON Analysis Results

bash
python3 scripts/analyze_codebase.py /path/to/project --json

Parameters

Parameter	Description
`directory`	Code directory to analyze (required)
`--type, -t`	Diagram type: `architecture`, `flowchart`, `org`, `all` (default: `all`)
`--output, -o`	Output directory (default: current directory)
`--format, -f`	Output format: `mermaid`, `svg`, `both` (default: `mermaid`)
`--max-files`	Maximum number of files to scan (default: 500)
`--max-depth`	Maximum depth for org chart (default: 4)
`--json`	Output analysis results in JSON format

How It Works

Scan phase: Recursively traverse the directory, skipping node_modules, .git, __pycache__, etc.
Parse phase:
- Python files: uses the ast module to parse import and from ... import statements
- JS/TS files: uses regex to match import, require, and export from
- Go files: uses regex to match import statements
- Java files: uses regex to match import statements
Resolve internal dependencies: Maps import paths to actual files within the project
Generate diagrams: Converts dependency relationships into Mermaid diagram syntax
Render (optional): Calls mmdc (Mermaid CLI) to render .mmd files as SVG

Use Cases

Quickly understand the module structure of an unfamiliar project
Visualize dependencies during code review
Create architecture diagrams for technical documentation
Detect circular dependencies or excessive coupling
Analyze project structure before refactoring

Dependencies

Python 3.7+ (standard library only, no extra packages needed)
SVG output requires @mermaid-js/mermaid-cli (optional)

Notes

Only analyzes static import relationships; dynamic imports are not tracked
For large projects, use --max-files to limit the scan scope
Mermaid diagrams with too many nodes may be hard to render; use --type to generate diagrams separately

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

scripts/analyze_codebase.py17 KB

Frequently asked questions

What does the Code To Diagram AI skill do?

Why use Code To Diagram on TypingMind?

Because you install it once and use it with any model. Code To Diagram is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Code To Diagram in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zebbern/claude-code-guide/tree/main/skills/code-to-diagram. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Code To Diagram?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Code To Diagram?

As many as you like. As long as a model supports skills, you can use Code To Diagram with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Code To Diagram AI skill free?

Yes. It is published on GitHub by zebbern under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Systematic Debugging

obra

CommunityPopular

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Using Git Worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Code to Diagram

Usage

Basic: Analyze an Entire Project

Specify Diagram Type

Specify Output Directory and Format

Output JSON Analysis Results

Parameters

How It Works

Use Cases

Dependencies

Notes

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now