Draft customer-facing release notes from your issue tracker

Pulls completed issues from Linear and has Claude draft customer-facing release notes for your team to review.

How the work actually flows

A straight line. Runs once per each completed issue.

Pattern: Sequence (1) · Multiple Instances with a priori Run-Time Knowledge (14) · Transient Trigger (23)

flowchart TD trig>"release notes label added"]:::trig s0["Find issues completed since last release"]:::task s1[["Gather customer-tagged issues"]]:::mi s2["Claude drafts changelog entries"]:::svc s3(("Post draft for team review")):::human trig --> s0 s0 -->|"one per each completed issue"| s1 s1 --> s2 s2 --> s3 out[/"draft changelog ready for review"/]:::out pay{{"time saved writing release notes"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceRuns once per itemA personResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
DevOps & IT Operations
Connects
GitLabLinearClaude

The problem it solves

Writing release notes means digging through tickets to remember what actually shipped and rewriting technical jargon into something a customer can understand. That work usually falls to whoever has time, not whoever knows the details best.

Who it fits

Product and engineering teams that publish customer-facing release notes.

How it works

  1. A release note merge request is labeled to start the process
  2. The system checks your release feed and finds all issues completed since the last release
  3. Completed issues with customer-relevant tags are gathered from Linear
  4. A summary of those issues is posted for review
  5. Claude drafts customer-facing changelog entries grouped by enhancements and fixes
What you get

A drafted changelog grouped by fixes and features

Completed issues since your last release get pulled together and drafted into a customer-facing changelog, grouped neatly by enhancements and fixes for your team to review.

What you get

A draft changelog, grouped into enhancements and fixes, posted for your team to review before publishing.

What you need

A GitLab account, a Linear account, and an Anthropic API key.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Get an AI risk report on every code change before it's merged

It reviews every code change automatically and flags risks, bugs, and test gaps before you merge.

Advanced

Turn a task comment into instant AI-powered market research

Type a command like search or trends into a task, and the system researches the web and posts AI analysis back as a comment.

Advanced

Turn GitLab webhook notifications on or off from a simple form

Submit a repository link and the system toggles its webhook connection on or off automatically.

Advanced

Get AI-assisted first-pass reviews on every GitLab merge request

Three AI reviewers scan each code change for bugs, security risks, and maintainability issues before a human looks at it.

Advanced
Back to the AI Playbook