Project Leader
Release notes from the commits, not from memory at 17:45
Reads everything since the last release tag, sorts features from fixes from noise, and leaves a customer-readable draft on your desk to edit.
Release notes get written at the worst possible moment, right before the release, from memory. Which is how the feature that took three weeks shipped unannounced and the changelog entry says "various improvements."
How it works
- 01
Clone the repository into the agent's workspace once. When notes are due, on a schedule or on request, it pulls, lists every commit since the previous release tag, and sorts them: features, fixes, and internal changes a customer never needs to hear about. Terse commit messages get rewritten into sentences a customer can act on, the noise gets dropped, and anything it cannot confidently classify is flagged for your call rather than guessed at.
- 02
The draft lands as a desk document, and a Slack message points at exactly the items that need a human judgment. The hour of scrolling history becomes a five-minute review, which is roughly the difference between release notes existing and not.