update-doc

To sync monorepo documentation with code changes, you need a tool that detects affected doc scopes via git diff and updates READMEs, CLAUDE.md files, and VitePress docs to match the current codebase. This preserves existing file style while correcting stale references.

Preventing stale documentation in a monorepo requires scanning all core doc locations after code changes to catch outdated file paths, renamed APIs, and removed features. Post-update validation then ensures no broken path references remain in the updated files.

Yes, updating VitePress docs and CLAUDE.md convention files together is possible using multi-scope documentation scanning. It automatically identifies all affected documentation assets across the monorepo and aligns them with the modified API endpoint structure.

Documentation staleness detection for auto-translated German docs works by applying special handling during the synchronization process, ensuring translated content aligns with recent code changes while preserving the original detail level and file style.

Documentation synchronization preserves the existing writing style of project READMEs by detecting affected scopes and applying updates that match the current code. It maintains each file's original detail level rather than overwriting it with a uniform format.

Using git diff to detect affected documentation scopes limits updates to tracked code changes within the monorepo. It requires code to serve as the single source of truth and may not catch undocumented behaviors or changes outside the detected diff paths.