Skip to main content
Every week, pull changes from GitHub and Linear, generate customer-facing release notes grouped by New, Improved, and Fixed, and publish them in Notion. Skip internal-only chores and flag anything that looks like a breaking change, so product, support, and customers share one story on a regular cadence.

Best for

  • Product managers who need a weekly changelog without waiting for a version tag.
  • Product marketing and support who need the same story as customers.

Connectors

Before you start

Point Agent at the repo and Linear team. Connect Notion for the published page. Say which day the weekly run should happen.

Prompt the agent

What to expect

Agent drafts last week’s notes from pull requests and issues, then writes a Notion page. Edit the voice before you send them to customers. Skip anything that looks like an internal chore, and put breaking changes at the top. Compare the page to last week’s merged pull requests before you publish.

Make it work for you

Troubleshooting

  • Internal chores show up in the notes: point Agent at the right repo and Linear team, and ask it again to skip chores that never ship to customers.
  • A breaking change was buried: tell Agent what “breaking” means for you (login, billing, or a required migration) and ask it to put those items at the top, flagged.
  • The Notion page is the wrong one: give the exact page or database link, and say whether to overwrite last week’s notes or create a new page each run.

Source candidates

Same GitHub connector for hiring, not shipping.

Analyze customer feedback

For product managers who also review tickets in Notion.