update-doc

To automatically update documentation after code changes, you can analyze git diffs to map modified files to documentation concepts and refresh impacted references. This keeps docs in lockstep with the codebase without manual maintenance.

Keeping developer docs in sync with git commits involves analyzing recent commits to detect changed files, updating impacted documentation entries, and regenerating the index. This prevents documentation drift after merging feature branches.

Auto-syncing documentation from a git diff targets projects using the llmdoc format. The process maps code changes to llmdoc concepts and updates the corresponding references to ensure the documentation index remains consistent.

To regenerate a documentation index after modifying code, you re-scan the llmdoc directory to ensure consistency. This automatically identifies impacted concepts from git diffs and refreshes the index to match the latest codebase state.

You should run an automated documentation update when you merge a feature branch or complete code changes. It analyzes recent commits, updates affected llmdoc entries, and reports changes to prevent manual maintenance and drift.