document-release

To keep documentation synchronized with shipped code changes, you can automate post-ship updates that diff released code against current docs and update text accordingly. This ensures README, ARCHITECTURE, and CLAUDE.md reflect the actual shipped state.

The best way to update README and ARCHITECTURE files after a release is running an automated documentation sync workflow. It cross-references shipped changes with existing project docs and applies targeted edits to keep project narratives consistent.

Post-ship documentation drift prevention works by reading project docs, cross-referencing recently merged changes, and using deterministic Bash, Read, Write, and Edit tools to update text. This aligns CHANGELOG and architecture references with the current ship cycle.

Yes, you can align CLAUDE.md with your latest code release. The skill ensures CLAUDE.md and architecture references describe the current state after shipping by diffing shipped code against current docs and applying necessary text updates.

No specific dependencies are required to automate changelog polishing and doc updates. The skill relies on standard SKILL.md frontmatter for configuration and uses built-in Bash, Read, Write, and Edit tools to execute a deterministic documentation update workflow.

You should not use automated documentation sync when your project lacks established core docs like README or ARCHITECTURE files, as the tool requires existing documentation to diff against shipped code changes and apply targeted text edits.