Agent skill · Workflow

Release notes from merged PRs

Sorts merged pull requests into new, improved, fixed and breaking, drops internal-only work, writes a changelog, an in-app note and a short post in parallel, then waits for your approval. Use when asked to run the "Release notes from merged PRs" workflow.

The release-notes-from-merged-prs/ folder with SKILL.md.

The skill itself. Agents read the name and description first and load the rest only when a task matches.

release-notes-from-merged-prs/SKILL.md
---
name: release-notes-from-merged-prs
description: Sorts merged pull requests into new, improved, fixed and breaking, drops internal-only work, writes a changelog, an in-app note and a short post in parallel, then waits for your approval. Use when asked to run the "Release notes from merged PRs" workflow.
---

# Release notes from merged PRs

Sorts merged pull requests into new, improved, fixed and breaking, drops internal-only work, writes a changelog, an in-app note and a short post in parallel, then waits for your approval.

## Inputs

Ask for any of these that the user hasn't given:

- `changes` (e.g. "#412 Add tags and custom fields to CSV export
#415 Bump eslint to 9.x
#418 Fix 500 when saving a prompt with an emoji in the title
#420 BREAKING: /api/v1/prompts now paginates (limit 50, cursor)
#421 Refactor search tokenizer")
- `version` (e.g. "2.4.0")
- `product` (e.g. "Acme Prompts")

## Steps

Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.

1. **Paste the changes** — Start: Start with {{changes}} for {{product}} {{version}}.
2. **Sort and rewrite the changes** — Load the `release-notes-writer` skill, then: Sort each change in {{changes}} into New, Improved, Fixed, Breaking or Internal. Rewrite every kept change as one line about what users can now do. For each breaking change, write who is affected and the exact migration steps. List the Internal items you dropped at the end. Save the result as `grouped`.
3. **Three versions** — Launch these as parallel subagents in one message, then wait for all of them. Write your version for {{product}} {{version}} from {{grouped}} only. Leave out Internal items. Save the result as `notes`.
   - **Changelog**: A Markdown CHANGELOG.md entry: '## {{version}} (date)', a one-sentence summary, then New, Improved, Breaking and Fixed sections with PR numbers.
   - **In-app note**: Under 60 words for a what's-new panel: the change most users will notice, and one link placeholder [link].
   - **Short post**: Under 280 characters for social or a community channel, leading with the most useful change. No hashtags.
4. **Check before publishing** — STOP and ask the user to approve before continuing: Show {{notes}}. Approve, edit any version, or reject.
5. **Return the notes** — Finish: Return {{notes}}: the changelog entry to add to CHANGELOG.md or the GitHub release, and the other two to copy.

## Done when

Every step has run, each approval was given, and you've reported what was produced and where it was saved.