document-release

To automate documentation updates after a code release, you can use a skill that reads code changes and edits markdown files. It reviews differences to automatically update README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to match shipped code.

Keeping a changelog consistent with shipped code involves cross-referencing code changes and polishing the changelog voice. This skill automates that process, cleaning up TODOs and optionally bumping the project version during release workflows.

Yes, you can sync README and ARCHITECTURE markdown files automatically by running a documentation synchronization tool. It cross-references differences in shipped code and edits key markdown files to ensure accurate, up-to-date project documentation.

Yes, scripting and file editing capabilities are required to maintain documentation accuracy. The automated synchronization process relies on scripts to read project docs, cross-reference differences, and edit text and markdown files.

You should update project documentation immediately after a release to prepare for the next development cycle. Running an automated documentation sync ensures your files reflect the latest shipped features and fixes, reducing manual oversight.

Project documentation falls out of sync after shipping due to manual oversight when updating multiple files. Automating the process by reviewing code changes and editing markdown files ensures consistency between shipped code and associated documentation.