sync

To keep CLAUDE.md documentation in sync, the skill detects and applies changes in dependencies, directory structures, commands, and file references by auditing root, module, and rule files against package managers, git, and filesystem states.

Your CLAUDE.md file experiences documentation drift when updates to package manifests or directory structures are not reflected in the documentation. The sync skill automatically detects this drift and applies the correct updates.

The best way to automate CLAUDE.md updates is running the sync skill, which parses package manifests and applies detected dependency changes directly to your root, module, and rules documentation files.

The sync skill works with both root and module-level CLAUDE.md files, auditing rule files against actual codebase states using file system traversal, version control, and package manifest parsing.

You should run drift detection after updating dependencies in package.json or refactoring a directory structure, ensuring your documented commands, file paths, and dependencies accurately reflect the current codebase.

Yes, synchronizing CLAUDE.md requires tools for file system traversal, version control via git, and package manifest parsing to successfully audit and update documentation against the current codebase state.