document-release

To prevent documentation drift, you need to audit and update project documentation to match committed code changes. This skill triggers via commands like 'update docs' to ensure README, CHANGELOG, and architecture files accurately reflect the codebase before merging.

The best way to sync documentation is running a comprehensive audit that checks README, ARCHITECTURE, CONTRIBUTING, CHANGELOG, CLAUDE.md, TODOS, and VERSION files against committed code changes. This ensures all critical documentation remains consistent with the codebase.

You should run a documentation update after code changes are committed but before merging your pull request into the main branch. This timing ensures all project documentation is updated and accurate before changes are integrated into the main codebase.

The 9-step documentation audit process works by systematically detecting and correcting inconsistencies between your codebase and project files. It covers all critical documentation files to ensure no documentation drift occurs and maintains strict consistency between code and documentation.

Yes, you can use this documentation sync tool without external dependencies. It operates independently using internal scripts to audit and update documentation, ensuring accuracy with committed code changes without requiring additional project management or version control packages.

Yes, the documentation update explicitly covers CONTRIBUTING and VERSION files, alongside README, ARCHITECTURE, CHANGELOG, CLAUDE.md, and TODOS files. This comprehensive coverage ensures all critical project documentation stays synchronized with committed code changes.