chat-release-notes

You can convert GitHub release notes into editor-ready documentation by refining CI-generated bullets and rewriting them in a consistent editorial voice, then saving the draft locally for review. The process cross-references PR bodies and deployment sources to assemble a coherent Deployment Changes section.

The best way to assemble a Deployment Changes section is by aggregating changes described in relevant PR bodies alongside deployment sources like apps/chat/README.md. This cross-referencing ensures the final section accurately reflects all deployment modifications.

To rewrite auto-generated release bullets for a stakeholder audience, classify them into meaningful groups like features and fixes, then rephrase each bullet in a concise, publish-ready voice. This ensures the documentation is accessible to both developers and stakeholders.

Yes, you can generate release notes for a specific GitHub pre-release tag by providing the tag name such as 0.45.0-rc.55. The system reads the CI-generated bullets for that tag and produces a draft saved to claude/release-notes/.

Yes, the release notes workflow preserves PR and issue references while rewriting the text into an editorial style. This ensures that traceability to the original GitHub pull requests and issues is maintained in the final draft.