code-to-docs
Analyze a codebase and generate an Obsidian-native documentation vault — architecture diagrams, API references, a codebase health assessment, and teaching-focused explanations at three audience levels — then keep it current with incremental git-diff updates and read-only session digests.
Plugin code-to-docs from marketplace code-to-docs-skill in SDS-Mode/code-to-docs-skill. Commands read from the repo's manifest — 1 month ago.
What it installs
Skills (4)
code-to-docs-digestLoad existing code-to-docs vault context into the conversation before coding. Read-only — never writes files. Provides architecture overview, module summaries, known issues, and session history. Use when starting a coding session, loading doc context, or catching up on a documented codebase.
code-to-docs-hooksInstall or remove project-level automation hooks for the code-to-docs lifecycle. Setup adds SessionStart (digest on session start) and PostToolUse (update hint after git commits) hooks. Teardown removes only code-to-docs hooks. Use when someone wants to automate doc updates, set up hooks, or remove
code-to-docs-updateIncrementally update an existing code-to-docs vault after coding changes. Diffs against the last documented commit, re-analyzes only affected modules, merges with existing docs, and tracks issue resolution. Use when someone says update docs, sync docs, refresh documentation, or after making code cha
code-to-docsUse when generating documentation from a codebase, creating architecture docs, building an Obsidian vault from code, or when someone asks to document or explain a project's structure
Maintain code-to-docs?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.