Release changelog agent that publishes GitHub PRs to Confluence and Notion

Resolves the release range from repo tags, collects the pull requests merged in it, groups them into features, fixes, and chores, and links each Linear issue. Every call runs as the release manager who owns the release, never a shared CI bot.

Release changelog agent

Sample Agent for Acme

May 22 · 10:00 AM ·

47s

Draft the v2.4.0 changelog and publish it

R

Comparing v2.3.0...v2.4.0 in scalekit-inc/platform

Release range resolved

github_tags_list

26 merged pull requests collected

github_commits_compare

Changelog published

confluence_page_create

Release notes - platform v2.4.0

26 pull requests in this range

Grouped into 9 features, 11 fixes, 6 chores

Every entry linked to its GitHub PR and Linear issue

Delivered

Confluence page created in space SD, under Releases

Notion doc published, a version already published is skipped

Message Claude...

Trusted by teams shipping agents to production

Release changelog agent

Sample Agent for Acme

May 22 · 10:00 AM ·

47s

Draft the v2.4.0 changelog and publish it

R

Comparing v2.3.0...v2.4.0 in scalekit-inc/platform

Release range resolved

github_tags_list

26 merged pull requests collected

github_commits_compare

Changelog published

confluence_page_create

Release notes - platform v2.4.0

26 pull requests in this range

Grouped into 9 features, 11 fixes, 6 chores

Every entry linked to its GitHub PR and Linear issue

Delivered

Confluence page created in space SD, under Releases

Notion doc published, a version already published is skipped

Message Claude...

How agent builders go from zero to a published changelog in six steps

A real working agent you can deploy

This repo keys every connected account on per-connector GITHUB_USER, LINEAR_USER, CONFLUENCE_USER, and NOTION_USER identities, defaulting to one release manager's email. In production, pass each user's real ID as the identifier on every Scalekit call, and send them an authorization link whenever their connector status is not ACTIVE.

Agents that write release notes, without the auth plumbing

Four things you'd otherwise build: GitHub token storage, Linear OAuth, Confluence and Notion tokens, refresh. Handled.

1

Install

terminal

terminal

terminal

terminal

2

Prompt

Why choose Scalekit

Delegated identity. Not service accounts.

Credentials never touch agent code or LLM context. The agent acts as the user, not as a shared bot.

Delegated OAuth - Agent reads your calendar, your inbox — scoped to the authorizing identity, not org-wide.

Credentials outside agent runtime - Tokens never touch agent code or LLM context. Both failure modes covered.

Token lifecycle automatic - Refresh, expiry, rotation across all connectors. One SDK call. Zero management code.

200+ prebuilt connectors - Google, Slack, HubSpot, GitHub, Jira, Notion, Salesforce — same auth pattern everywhere.

Try other Agent Templates

Prebuilt agents you can ship today

Each one runs on delegated identity, scoped per user.

ENGINEERING

DevOps assistant agent

Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.

ENGINEERING

Engineering standup agent

Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.

ENGINEERING

Auto-release notes agent

Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.

ENGINEERING

Slack triage agent

Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.

SUPPORT

Support triage agent

Classify new Zendesk tickets, search the Notion knowledge base for an answer, and route what it cannot resolve to Slack.

GTM

Competitive intelligence briefing agent

Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.

Connectors used

+100 more

Build your own
‍multi-connector agent

Add connectors. Change the LLM. Same delegated auth pattern.