document-release

To keep documentation in sync with shipped releases, you can run a post-ship automation skill that reads code diffs and updates core markdown files like README and ARCHITECTURE to reflect the actual shipped changes.

Updating a markdown changelog after shipping is best handled by automating diff analysis to polish existing changelog entries, ensuring post-ship governance by preserving history and enforcing consistency across all project documentation.

Yes, this release management skill operates directly on core markdown docs including README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md, aligning their content with the shipped code changes to prevent documentation drift.

To tidy TODOS and bump VERSION files after a release, use a post-ship documentation skill that optionally updates version numbers and cleans up todo lists to reflect completed work alongside standard documentation updates.

Yes, you can use diff analysis to prevent post-ship documentation drift by automatically reading shipped changes and applying those updates to core documentation files, ensuring changelog history and project docs remain consistent.