Weekly Linear to GitBook release notes, with Slack review

Every Friday at 3pm ET, draft this week's release notes in GitBook from completed Linear issues, then ping engineering in Slack so they can review and merge.

Step 1. Pull issues from Linear. Use Linear List Issues to find every issue that moved to a Done state in the last seven days. Skip any issue carrying the label "internal" or "infra" — those should never reach customer-facing release notes.

Step 2. Group and rewrite. Sort the remaining issues into four sections: Features, Improvements, Bug Fixes, Breaking Changes. Decide which section an issue belongs in based on its labels first, then fall back to the issue title and description if labels are ambiguous. Collapse multiple issues that ship the same user-visible feature into a single bullet so customers do not see the same change three times. For each bullet, write one or two plain-English sentences describing the user-visible impact, not the engineering work. No PR numbers, no Linear IDs, no internal codenames, no jargon.

Step 3. Stage the draft in GitBook. Use GitBook Create Change Request against our designated Release Notes space to open a draft containing a new page titled with this week's date (for example, "Release notes for the week of June 23, 2026"). Lay out the page as one heading per section with bullets underneath; if a section is empty, omit the heading. The change request stays a draft — do not merge it. Editing the language before publish is the point.

Step 4. Notify engineering. Use Slack Send a Message (Slack Bot) to post in the engineering channel with a one-line summary of how many items shipped in each section and a link to the GitBook change request so a teammate can review, polish the language, and merge it to publish.

If no issues moved to Done this week, skip creating the change request and instead send a short Slack note saying nothing shipped, so the team knows the workflow ran and there was simply nothing to publish.

Tone: customer-facing, friendly, no internal jargon, no engineering acronyms. The reader is a product user, not a developer.

Additional information

What does this prompt do?

Every Friday afternoon, pulls the Linear issues your team marked Done in the past seven days.
Groups them into Features, Improvements, Bug Fixes, and Breaking Changes, and rewrites each one in plain customer-facing language so it reads like a changelog and not an engineering ticket.
Opens a draft release notes page as a change request in your GitBook Release Notes space, dated for this week, so nothing goes live until someone reviews it.
Posts a one-line summary and the draft link to your engineering Slack channel so the team can edit the language and merge when it looks right.

What do I need to use this?

A Linear workspace where engineering tickets land
A GitBook space set aside for release notes
A Slack channel where engineering watches for review pings

How can I customize it?

Change the day and time the notes get drafted (defaults to Friday at 3pm).
Adjust which Linear labels are skipped (defaults to internal and infra so private work never reaches customers).
Pick the GitBook space and the Slack channel that receive the draft and the review ping.

Frequently asked questions

Will this publish straight to customers?

No. GitBook edits flow through a change request, so the workflow only opens a draft. Someone on your team has to merge it before customers see anything, which gives you a chance to tweak the wording.

What happens in a week where nothing shipped?

If no Linear issues moved to Done in the past seven days, the workflow skips creating a draft and posts a short note in Slack so you know it ran and there was nothing to ship.

How does it decide what counts as a Feature versus a Bug Fix?

It looks at Linear labels first (things like feature, improvement, bug, breaking) and falls back to the issue title and description when labels are missing. You can teach it your team's exact labels when you set it up.

Will internal or infrastructure work end up in customer release notes?

Issues labelled internal or infra are skipped by default. You can add more labels to the skip list when you set the workflow up.

Does it collapse duplicate work into one bullet?

Yes. If multiple Linear issues ship the same user-facing feature, the workflow merges them into a single bullet rather than listing each ticket separately.