document-release

Automating documentation updates after a release involves reading shipped diffs and updating core project files like README, ARCHITECTURE, and CONTRIBUTING to reflect the actual changes. This ensures docs stay aligned with the codebase without manual rewriting.

Polishing a changelog and bumping a version number from a feature branch requires analyzing the committed diff to refine the release language. The process enforces safe edits on a separate branch and prompts for version decisions before generating a PR body preview.

Yes, you can automatically tidy TODOs and update CLAUDE.md based on shipped code changes by running an automation skill on your feature branch. It reads the release diff to clean up outstanding tasks and synchronize AI context files.

Automated release management can function without external dependencies or components by operating natively within your repository. It processes diffs, polishes changelogs, and manages version bumps entirely through internal logic on your feature branch.

You should avoid automated documentation updates when your release requires highly nuanced architectural explanations or manual narrative adjustments that exceed the scope of standard diff-based polishing, changelog tidying, and version bumping.

Post-ship documentation automation handles version bumping by prompting you for version decisions directly when needed. It operates safely on a feature branch, ensuring the version bump is reviewed before producing a concise PR body diff preview.