Automate daily changelogs
Generate reviewable summaries of repository activity on a schedule.
Use a daily workflow to prepare a changelog draft for humans to review, instead of someone combing through a day's merges by hand.
Workflow shape
- Set the schedule to once per day (weekdays-only if weekends are quiet for your repo).
- Ask the agent to gather merged pull requests, closed issues, and commits since the last run.
- Have it group changes by product area and audience- user-facing versus developer-facing, for example.
- Tell it to flag anything uncertain, sensitive, or worth a second look for human review instead of guessing.
- Publish only after someone approves the draft.
The editor's Use template shortcut includes a "Draft release notes" starting point that covers most of this out of the box- start there and narrow the prompt to your repo's conventions.
Daily changelog workflow configuration
A workflow set to a daily schedule with a prompt asking the agent to draft a changelog from the day's merged pull requests.
Good changelog output
Good changelog automation is concise, sourced, and easy to edit. Ask the agent to include:
- User-facing changes.
- Developer-facing changes.
- Fixes and reliability work.
- Links to the source pull requests or issues.
- Open questions for the reviewer.
Reviewing a run
Every run creates its own workspace with the full transcript: what the agent read, the draft it produced, and any tool calls it made along the way. Open the run from the workflow's run history, read the draft where the agent left it (as a file in the workspace, or as a reply in the session), and edit it before it goes anywhere.
If more than one person owns changelog quality, set the workflow's owner to Team instead of Personal- see team-wide workflows for what changes.