THE USE CASE
Where this helps.
Help stakeholders understand what changed. Summarize merged pull requests and release commits into verified notes.
How to try it responsibly
- 01
Collect only merged changes intended for the release.
- 02
Categorize breaking changes, fixes, and customer-visible features.
- 03
Ask engineering owners to verify claims before publishing.
A starting prompt
STARTING TEMPLATE / ADAPT TO YOUR CONTEXT
Using the listed merged PRs, summarize user-visible changes and note gaps requiring confirmation.
How to verify the result
Check every item against merged code and rollout status.
Limits and failure cases
A merged pull request may not be deployed or enabled for every user.
Editorial note: This is a practical starting example, not an independent performance benchmark or a guarantee that a specific product can complete the workflow autonomously. Test with your own permissions, tools, and representative cases. Relevant technical/reference source ↗