Write customer-facing release notes from my changelog
Polished release notes grouped by what users care about, not by commit order
Write customer-facing release notes from this raw material: [paste changelog, commit list, or merged PR titles — or link a public GitHub releases page]. Translate engineer-speak into user outcomes: 'Refactored auth middleware' becomes nothing (skip it); 'Fix: dashboard crash on empty state' becomes 'Fixed a crash when opening an empty dashboard'. Group items into New, Improved, and Fixed. Lead each item with the user benefit, name features the way the UI names them, and keep each entry to one or two sentences. Skip internal changes, dependency bumps, and anything users cannot perceive — but list what you skipped at the bottom so I can rescue anything you misjudged. Tone: [e.g. friendly but not jokey]. Add a two-to-three sentence highlights intro covering the release's theme. Target under 400 words total.