document-release

Automating documentation updates after a code release requires synchronizing project files like README and CHANGELOG with the latest deployment state to prevent documentation drift. This skill handles that by integrating git and file system operations to automatically align docs post-ship.

Documentation drift happens when project docs become outdated relative to the codebase. You can prevent it after merging a feature branch by running an automated synchronization process that updates architecture diagrams, README, and CLAUDE.md files to reflect the current deployed state.

Yes, you can automatically sync your CHANGELOG and architecture diagrams before finalizing a release. The skill detects architecture diagram drift, cleans up TODOs, and polishes CHANGELOG entries using a sell-test rubric to ensure everything is perfectly aligned with the new code.

Yes, automated changelog maintenance works without external dependencies. The skill operates using integrated git and file system operations to manage versioning and documentation sync, requiring no additional external libraries or packages to function within your software development workflow.

The best way to reduce documentation debt in a software development workflow is to automate post-ship synchronization of README, ARCHITECTURE, and CLAUDE.md files. This ensures documentation consistently matches the deployed codebase without adding manual labor.

You should not use automated documentation synchronization if your project lacks a git repository or standard file system structure, as the skill relies on integrated git and file system operations to detect drift and update configuration files during the release process.