CONTENT CREATION

Customer-Impact Changelog Curated by an Agent

An agent reads PRs merged since the last tag, decides which actually matter to customers, drafts plain-English entries with impact framing.

CategoryContent Creation
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew git tag pushedGitHubGitHub
  • ActionFetch merged PRs with descriptions and labelsGitHubGitHub
  • LogicAgent scores and filters by customer impact
  • ActionWrite impact-first entries for relevant PRs
  • ActionCommit curated changelogGitHubGitHub
  • OutputDeploy microsite on VercelVercelVercel

What it does

Uses an agent to do the judgment work a human normally does on changelog day: reading each merged PR, deciding whether a customer would care, and explaining the impact rather than the implementation. Internal refactors and dependency bumps are filtered out; the surviving changes are rewritten into benefit-led entries and published.

When to use it

Use it when your PR stream is noisy and a naive title-to-bullet changelog would bury the few changes customers actually notice. Best when you want curation, not just transcription.

How it works

  1. 1A new tag push starts the run.
  2. 2The agent pulls the PRs merged since the prior tag, including descriptions and labels.
  3. 3It scores each PR for customer relevance and drops the internal-only ones.
  4. 4For the relevant set it writes impact-first entries, grouped by who they affect.
  5. 5The curated changelog is committed to the content repo.
  6. 6Vercel deploys the microsite and the run reports what it included and skipped.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect VercelDeploys, runtime logs, analytics.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.