wiki-refresh

To incrementally update documentation, identify changes in high-level facts across multiple repositories and apply conservative updates only to affected pages. This preserves accuracy while preventing unnecessary rewrites of existing content.

Refreshing documentation conservatively means detecting which high-level facts changed in the codebase and updating only affected pages. Pages that already accurately represent the current state remain untouched, avoiding unnecessary modifications.

Yes, documentation refresh supports multi-repo project structures by identifying high-level fact changes across multiple repositories and applying targeted updates to affected pages, maintaining accuracy across the entire project.

Documentation pages needing updates are identified by detecting changes in the high-level facts of the codebase across multiple repositories, then applying conservative updates only to those specific affected pages.

Conservative documentation updates require direct access to the codebase and documentation files, and focus on incrementally changing existing pages rather than generating entirely new content, limiting scope to maintaining current page accuracy.