Agent Templates
Release changelog agent

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.

01
Authorize GitHub, Linear, Confluence, and Notion
connectors.py
Step 0 checks all four connected accounts before a single changelog line is rendered. Anyone whose connector is not ACTIVE gets a Scalekit authorization link and completes OAuth themselves; tokens stay in the vault, never in this repo.
connectors.py
resp = self.actions.get_or_create_connected_account(
    connection_name=self.connector_name,      # github / linear / confluence / notion
    identifier=self.identifier,                # the release manager, not a CI bot
)
if resp.connected_account.status != "ACTIVE":
    link = self.actions.get_authorization_link(
        connection_name=self.connector_name,
        identifier=self.identifier,
    ).link
    logger.warning(f"Authorize here: {link}")
02
Resolve the release range from repo tags
provisioning.py
03
Collect the pull requests merged in the range
run_flow.py
04
Group by feature, fix, and chore, then link Linear
changelog.py
05
Publish to Confluence, once per version
run_flow.py
06
Publish to Notion and record what shipped
state.py

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
claude plugin marketplace add scalekit-inc/claude-code-authstack && claude plugin install agent-auth@scalekit-auth-stack
terminal
curl -fsSL https://raw.githubusercontent.com/scalekit-inc/codex-authstack/main/install.sh | bash
terminal
copilot plugin marketplace add scalekit-inc/github-copilot-authstack
copilot plugin install agent-auth@scalekit-auth-stack
terminal
curl -fsSL https://raw.githubusercontent.com/scalekit-inc/cursor-authstack/main/install.sh | bash
terminal
npx skills add scalekit-inc/skills --skill integrating-agent-auth
2
Clone github.com/scalekit-developers/workflow-agents-demos/tree/main/release-changelog-agent and adapt it for my release process.

I am building for: my engineering org (or: a developer-tools product)   <- edit this line
Connectors my users need: GitHub, Linear, Confluence, Notion   <- edit this line
Trigger: invoked per release tag from CI. Deliver: a grouped changelog published to a Confluence page and a Notion doc, every entry linked to its PR and its Linear issue.

Steps:
1. Create Scalekit AgentKit connections for github, linear, confluence (the plain REST connector, not AtlassianMCP), and notion -- copy the exact connection names into GITHUB_CONNECTOR / LINEAR_CONNECTOR / CONFLUENCE_CONNECTOR / NOTION_CONNECTOR.
2. Set GITHUB_USER / LINEAR_USER / CONFLUENCE_USER / NOTION_USER to the release manager each run acts for, so every write is attributed to a person instead of a shared CI bot.
3. Point GITHUB_OWNER / GITHUB_REPO at a repo with at least two tags; leave PREVIOUS_TAG and CURRENT_TAG empty to let provisioning.py resolve the range, or set them to pin it.
4. Set CONFLUENCE_SPACE_KEY and NOTION_PARENT_PAGE_ID, and turn off either target with PUBLISH_CONFLUENCE=false / PUBLISH_NOTION=false if I only publish to one.
5. Set LINEAR_TEAM_PREFIXES to my team keys so ABC-123 strings from other trackers are not mistaken for Linear issues, or ENABLE_LINEAR=false to skip enrichment.
6. Run python run_flow.py --dry-run to render the changelog without publishing, then describe how to wire it behind my tag-push CI job.
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.

Build your own
multi-connector agent

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