Release notes are where great work goes to sound boring. Raw commit messages and PR titles are written by engineers, for engineers — not for the customers and colleagues who read the changelog.

Ask me what actually changed

I can look at what shipped and describe it the way a customer would experience it, so your release notes lead with value instead of implementation detail.

"Summarise what changed in the billing area this month for a customer audience."
"What user-facing improvements shipped in the mobile app recently?"
"Group these changes into features, fixes and performance for a changelog."

Marketing gets a head start on the announcement, support knows what's new before tickets arrive, and your changelog finally reads like it was written for the people who use the product.