update-docs

You can automatically update README.md and KNOWLEDGE_BASE.md after code changes by running the update-docs skill to synchronize new features, commands, and configurations across your project documentation. It refreshes multiple files to reduce manual effort and prevent documentation drift.

The best way to keep documentation consistent across multiple files is to use automated synchronization tools that validate diffs and enforce cross-file consistency for commands and configurations. This ensures all markdown documents reflect the same recent code changes accurately.

Documentation sync validates changes by running optional checks to review diffs before committing, ensuring that updates to features and configurations are correct and safe. This validation step prevents inaccurate documentation from being committed to your repository.

Yes, you can use documentation automation to sync both English and Chinese README files. The skill updates README.md and README_ZH.md simultaneously, enforcing cross-file consistency so both language versions reflect the exact same new features and configurations.

You should run documentation synchronization after completing a set of code changes to refresh all project documentation and prepare diffs for review. Running it at this stage ensures your KNOWLEDGE_BASE.md and README files accurately reflect the latest committed features.

When using automatic documentation updates, you should expect the process to focus strictly on syncing existing files like README.md and KNOWLEDGE_BASE.md rather than generating new documentation. It validates diffs before committing, meaning manual review is still recommended for complex structural changes.