code-to-docs-skill

Load 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.

Install 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 hooks.

Use 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

Incrementally 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 changes.