doc-sync

To synchronize CLAUDE.md navigation indexes, you can audit the repository structure, detect documentation drift, and rebuild pure index tables for subdirectories to match the latest files. This ensures your navigation indexes accurately reflect the current repository layout.

The best way to update README architecture docs is to trigger a documentation synchronization process that reads existing CLAUDE.md files and applies architecture updates to README.md. This preserves original content while ensuring architecture information stays current with file modifications.

Yes, you can audit documentation drift within scoped boundaries like a specific directory or a single file instead of running a repository-wide audit. This targeted approach detects structural drift and applies updates only to the scoped section you specify.

Yes, doc-sync preserves original content while rebuilding pure index tables and updating README.md architecture sections. It reads your existing CLAUDE.md, audits the structure, and applies updates without overwriting your custom documentation or annotations.

To perform a repository-wide documentation audit, trigger a synchronization process that scans your entire repository structure, detects drift between CLAUDE.md navigation and actual files, and applies updates to both CLAUDE.md indexes and README.md architecture docs.