Example routine
Release notes draft
Turn merged pull requests into a user-facing changelog draft grouped by impact.
Use this routineSuggested rhythm
Twice a month
0 9 1,15 * *
America/Los_Angeles
Expected result
A publication-ready release notes draft grouped by impact, with source pull requests cited and open questions flagged.
Built for
Product · Content
Works with
- GitHub
What the routine does
Read pull requests merged in the connected repository {{repository}} since the last run. Group them into user-facing changes, fixes, and internal work, then draft release notes that describe each user-facing change by its impact rather than its implementation. Flag anything that needs a migration note or a screenshot, cite the source pull requests, and leave publication to human review or an explicitly approved tool.
Inputs
- Repository
{{repository}}The repository whose merged work to summarize.
Example: acme/web-app
Required MCP capabilities
- Read repository pull requests
Permission boundary
Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.
More content routines
Weekly
Blog research and drafting
Keep a publication schedule alive with sourced drafts that only need human review, not a rewrite.
Weekly
Notion content calendar review
Keep a content pipeline honest by comparing the plan in Notion with what actually shipped and what has quietly stalled.
Weekly
Google Drive source material digest
Keep writers grounded in the latest research, decks, and notes without reading every new file in the shared folder.
Weekly
Weekly topic brief (workflow)
Produce a weekly brief whose research, drafting, and packaging are separate reviewable stages rather than one prompt.