Changelog Broadcaster

How this loop works

Suggested schedule

Weekly · Mon ~9am

Loop type

Open loop — an ongoing monitor with no finish line.

Exit condition

Runs indefinitely (no finish line).

Notifications

On by default — you're alerted on each run's outcome (completion or failure). Silence with notify: never.

Ease of starting

Runs with almost no setup — confirm a detail or two and go.

When you see value

The first run drafts a changelog and social posts from the week's merges.

Set up a weekly loop that turns this project's shipped work into a changelog and announcement drafts. Before creating it, verify this machine can see the week's merged PRs and commits - gh or the git log - run one listing as a smoke test, and confirm with me which changes are worth announcing (user-facing features and fixes, not internal churn) and the voice and channels to draft for; never create a blind loop. Every Monday around 9am my local time, review what merged since the previous run - the loop keeps track of where the last one ended - distill it into one clear changelog entry grouped by feature, fix, and improvement in plain user-facing language rather than raw commit messages, and draft short social posts from it for the channels we agreed. Everything is a draft held for my review - never auto-post anywhere; drafting for approval is the whole point of this loop. Write the changelog entry and the post drafts as dated markdown with front matter `type: report`, a `title`, and `date` so they ride the calendar, and report the count of items shipped that week as a metric; a quiet week with nothing user-facing is a clean stop. Set up the loop's dashboard at creation: a calendar of the entries plus an embed of the newest one.