document-release

To update repository documentation to match shipped code, you need to cross-check existing docs against the latest diff and apply changes to affected files. This skill reads recent diffs to update README, architecture notes, and contributor guides so instructions match reality.

The best way to keep changelog wording accurate is to preserve existing content while validating factual changes and cross-references. This approach polishes release notes and flags risky narrative changes without overwriting previous entries.

Yes, you can sync README and contributor guides when post-release behavior changes by analyzing the shipped diff. The process updates affected Markdown files like CONTRIBUTING and CLAUDE.md to ensure they reflect the newly landed code.

Post-ship documentation cleanup does handle TODO removal and version bump validations by cleaning up stale items and asking for human judgment before applying version-related decisions. This ensures release hygiene without automated overrides.

You need to sync architecture notes and agent instructions after a release whenever the shipped behavior changed the codebase. Running a doc-to-code sync ensures that cross-references and path instructions match the actual merged code.