document-release

To automatically update README and CHANGELOG after a release, you can use a documentation synchronization tool that reads release diffs and applies non-destructive edits to keep docs aligned with shipped features.

The best way to sync project documentation with shipped changes is to use a diff-analysis workflow that automatically updates core docs like ARCHITECTURE and CONTRIBUTING, polishes the CHANGELOG, and cleans up TODOS.

Diff-analysis for post-release documentation updates works by reading the differences between code versions, then applying non-destructive edits to project files to ensure they reflect what was actually released.

Yes, you can automatically bump VERSION and clean up TODOS when shipping a release by running a post-ship workflow that evaluates changes and updates versioning consistency alongside documentation.

You need to update CLAUDE.md and CONTRIBUTING files after shipping when your release includes changes that affect project architecture, contributor guidelines, or core features, ensuring docs stay consistent with the shipped product.

Yes, non-destructive edits are applied when synchronizing docs with the latest release, ensuring that existing manual documentation content is preserved while automatically aligning descriptions with shipped features.