manage-codebase-refresh

To automatically update documentation for recent git changes, you can run an incremental refresh process that detects changed files via git diff and rewrites their corresponding doc sections. It uses a doc-index.json mapping to update only the affected documentation entries.

Incremental documentation refresh is the process of updating only the doc entries affected by recent code changes rather than rescanning the entire codebase. It maps changed git files to a doc-index and rewrites just those specific documentation sections.

To prevent documentation drift after a feature merge or refactor, run a codebase refresh to detect changed files and automatically rewrite the corresponding doc sections. This removes manual tracking and ensures docs reflect the current codebase state.

Yes, you need a .workflow/codebase/doc-index.json file mapping source files to documentation entries, and a state.json file for the baseline. The refresh process uses these to detect git changes and update the correct documentation sections.

Yes, you can use the --deep flag to force a broader contextual rescan of documentation instead of a standard incremental update. This ensures wider coverage when simple file-level change detection might miss related contextual shifts.

The codebase refresh determines the baseline for detecting changed files using the --since flag, the codebase_last_refreshed or codebase_last_rebuilt timestamp in state.json, or a 7-day fallback default. It then runs git diff against that baseline.