document-release

To update outdated project documentation after a merge, inspect the repository diff and edit README files, architecture notes, and contributor guides to match the shipped software changes and release status.

To synchronize a changelog with recent code changes, analyze the repository diff, improve the changelog wording, fill factual documentation gaps, and perform cross-document consistency checks against the shipped implementation.

The best way to ensure README and architecture documents match shipped code is to run a post-ship documentation synchronization workflow that performs repository inspection, diff analysis, and controlled versioning decisions.

You need to run a documentation cleanup workflow for a repository release after merging code changes to verify that project instructions, contributor guides, and factual documentation accurately reflect the shipped functionality and remaining tasks.

Yes, you can use repository diff analysis to fix factual gaps in contributor guides and project instructions by comparing recent code changes against existing documentation, editing outdated text, and applying consistency checks across the repository.