graph-export-mermaid

name	graph-export-mermaid
description	[Code Intelligence] Use when you need export a single file's knowledge graph as a Mermaid flowchart diagram in markdown.
disable-model-invocation	true
version	1.0.0

Quick Summary

Goal: [Code Intelligence] Export a single file

Workflow:

1. Detect — classify request scope and target artifacts.
2. Execute — apply required steps with evidence-backed actions.
3. Verify — confirm constraints, output quality, and completion evidence.

Key Rules:

• MUST ATTENTION keep claims evidence-based (file:line) with confidence >80% to act.
• MUST ATTENTION keep task tracking updated as each step starts/completes.
• NEVER skip mandatory workflow or skill gates.

Prerequisites

• Graph must be built first: run /graph-build if .code-graph/graph.db doesn't exist
• Requires Python 3.10+ with tree-sitter, tree-sitter-language-pack, networkx

Steps

1. Export file graph as Mermaid — Run via Bash (positional or --file flag both work):

   python .claude/scripts/code_graph export-mermaid <relative-path> --json
   # OR
   python .claude/scripts/code_graph export-mermaid --file <relative-path> --json
   

Default output: .code-graph/<path-based-unique-name>-graph.md (e.g., docs--project-config-graph.md)

2. Custom output path (optional):

   python .claude/scripts/code_graph export-mermaid <relative-path> -o custom-path.md --json
   

3. Report results: File path, node count, edge count.

Output Format

# Graph: src/auth.py

```mermaid
flowchart TD
 subgraph auth_py["auth.py"]
 login["login()"]
 validate["validate()"]
 hash_password["hash_password()"]
 subgraph AuthService["AuthService"]
 authenticate["authenticate()"]
 end
 end
 login -->|calls| validate
 login -->|calls| hash_password
 authenticate -->|calls| validate
```

What's Included

• Functions, classes, and test functions within the file
• Internal call relationships (both caller and callee in the file)
• Class membership shown via nested subgraphs
• Edge types: calls, imports, inherits, implements, tests, depends
• Non-code files (markdown, JSON): renders outgoing and incoming IMPORTS_FROM edges as a reference graph

What's Excluded

• External/stdlib function calls (e.g., parseInt, trim)
• Cross-file relationships for code files (callers from other files)
• CONTAINS edges (shown structurally via subgraphs instead)

Implicit Edge Types

Mermaid diagrams include implicit edges when present in the graph:

• MESSAGE_BUS edges show cross-service message flow
• TRIGGERS_EVENT edges show entity-to-event-handler relationships
• API_ENDPOINT edges show frontend-to-backend API connections

These edges are rendered alongside structural edges (CALLS, IMPORTS_FROM, INHERITS).

Use Cases

• Visualize a file's internal function call graph
• Understand code structure before refactoring
• Document architecture in markdown-compatible format
• Review file complexity and coupling

---

Export Graph as Mermaid Diagram

Export a single file's internal graph structure from .code-graph/graph.db as a Mermaid flowchart in a markdown file.

AI Mistake Prevention — Failure modes to avoid on every task:

Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal. Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing. Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain. Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path. When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site. Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code. Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks. Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis. Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly. Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.

MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.

Closing Reminders

• MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
• MANDATORY IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
• MANDATORY IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
• MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality

[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.