Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.
npx versuz@latest install vivekkarmarkar-claude-code-os-skills-obsidian-code-vizgit clone https://github.com/VivekKarmarkar/claude-code-os.gitcp claude-code-os/SKILL.MD ~/.claude/skills/vivekkarmarkar-claude-code-os-skills-obsidian-code-viz/SKILL.md--- description: Visualize a codebase as an Obsidian vault graph. Use when the user wants to understand code structure, call graphs, or architecture through Obsidian's graph view. Creates notes for functions/classes with wikilinks showing relationships. disable-model-invocation: true allowed-tools: Bash Read --- # Obsidian Code Visualization Visualize a codebase (or a single file) as an interconnected Obsidian vault using the Obsidian MCP. ## Arguments `$ARGUMENTS` — path to a file or directory to visualize. If empty, ask the user what to visualize. ## Steps ### 1. Determine scope - If `$ARGUMENTS` is a file: visualize that file's functions, classes, and their relationships - If `$ARGUMENTS` is a directory: visualize the key modules and their interconnections - If empty: ask the user ### 2. Determine project compartment Every visualization goes into a project-specific subfolder in the vault to avoid polluting the global graph. - Infer the project name from the git repo name, directory name, or ask - All notes go under: `<project-name>/code/` ### 3. Parse the code For each function, class, or significant code block: - Identify its name, purpose (one line), inputs, outputs - Identify what it calls (outgoing edges) - Identify what calls it (incoming edges) - Identify key data structures it operates on ### 4. Create notes via Obsidian MCP Each function/class becomes one note. Structure: ``` # function_name One-line purpose. ## Signature `def function_name(param1: type, param2: type) -> return_type` ## Calls - [[called_function_1]] - [[called_function_2]] ## Called by - [[caller_function_1]] ## Key details - Brief implementation notes only if non-obvious ``` ### 5. Create an overview note Create `<project-name>/code/Code Overview.md` that: - Lists all visualized components grouped by layer/concern - Links to each with wikilinks - Provides a 2-3 sentence architectural summary ### 6. Report to user Tell the user: - How many notes were created - The vault path where they live - Suggest they open Obsidian's graph view to see the structure