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

Turn the week’s product changes into a recurring release-notes workflow. Review the source scope and instructions before creating the routine.
1

Connect your tools

If needed, Agent prompts you to connect GitHub, Linear, and Notion. Name the repository, Linear team, and destination page or database. Say whether each run should create a new page or update an existing one.
2

Review and create the routine

Agent opens New routine with the title, schedule, time zone, and prompt filled in. Check Monday at 9:00 in your time zone. Confirm that internal chores are excluded and possible breaking changes are flagged, then select Create routine.
3

Receive your weekly release notes

Each run gathers GitHub and Linear changes, groups customer-facing notes under New, Improved, and Fixed, and writes them to Notion with source links. Results return to the same Replit chat. Review the notes before announcing or sending them to customers.
4

Find the routine and check its runs

Open Routines in the Replit sidebar. Select the run count to expand the history, use the play button to run it now, or use the switch to pause and resume the schedule.Compare the first Notion page with the week’s merged pull requests. Edit the voice, remove internal chores, and confirm breaking changes are prominent before sharing it.

​
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.