document-release

Keeping documentation in sync after a release requires updating your README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files. This Skill automates that post-ship process by cross-referencing code diffs to ensure all project docs accurately reflect the newly shipped changes.

Automating changelog updates and doc synchronization is best handled by a post-ship workflow tool. This Skill reads frontmatter settings, coordinates optional version bumps, and polishes the changelog voice alongside your core documentation to maintain project coherence.

Yes, you can update CLAUDE.md and CONTRIBUTING files automatically. The Skill targets these specific files alongside README and ARCHITECTURE docs, ensuring contribution guidelines and architecture decisions match the shipped codebase state.

You need to run post-ship documentation updates immediately after shipping a release. The Skill proactively suggests when a docs bump is warranted and outlines how to raise a PR to merge the synchronized changes into your main branch.

Yes, this docs-sync workflow supports automatic version bumps. It reads your frontmatter settings to coordinate optional version increments while simultaneously polishing TODO annotations and updating CHANGELOG entries to match the release state.

Your README drifts after shipping because manual updates are often skipped during rapid releases. This Skill prevents post-ship documentation drift by cross-referencing shipped diffs and automatically applying those changes across all key project docs.