A changelog for customers

Goal

Turn merged work since a tag into a customer-readable release page.

What you’ll have

Prompt

A changelog for customers

Your agent builds the page and checks the result with you.

Copy promptCopiedBuild a customer-readable changelog in Super Artifacts. Ask for the repository, starting tag, release version, date and existing page slug. Inspect merged work since that tag; exclude unfinished work and translate changes into customer benefits, fixes and upgrade steps. Read the changelog template with super_templates and fill its changelog slot, preserving earlier releases. Publish with super_publish to the same slug as a new version, explicitly private; keep it private with super_artifact_set and ask me for the intended audience. Return its link. Verify every entry against merged work, and check the existing slug before publishing so this remains one page.

Needs

• A repository, starting tag and release name.
• A connected agent and the changelog template.

Steps

1. 01

   A release boundary

   The agent finds merged work since the tag you supplied.

2. 02

   Words for customers

   Changes become short entries, with upgrade steps where needed.

3. 03

   One stable page

   The changelog slot holds the release history; publishing the same slug creates another version.

Check it worked

The link contains the new release and earlier entries. Versions shows a new version of the same artifact, with the newest one published.

If not

• An entry is inaccurate: The prompt asks the agent to trace it back to merged work.
• Two separate pages appeared: The prompt asks it to check the slug before the next publish.

Variations

• An unreleased section can show work awaiting release.
• A shorter page can announce only the latest release.

Next

• More on versions and publishing
• More on client update