Coding 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.

Prompt chainParallelHuman approvalRuns in Claude Code, Codex, GitHub Action

Running it here

Every step runs here with Claude when you're signed in, and in your own agent.

  1. TriggerPaste the changesStart with {{changes}} for {{product}} {{version}}.→ manual
  2. SkillSort and rewrite the changesSort 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.→ release-notes-writer
  3. ParallelThree versionsWrite your version for {{product}} {{version}} from {{grouped}} only. Leave out Internal items.
    • ChangelogA Markdown CHANGELOG.md entry: '## {{version}} (date)', a one-sentence summary, then New, Improved, Breaking and Fixed sections with PR numbers.
    • In-app noteUnder 60 words for a what's-new panel: the change most users will notice, and one link placeholder [link].
    • Short postUnder 280 characters for social or a community channel, leading with the most useful change. No hashtags.
  4. ApprovalCheck before publishingShow {{notes}}. Approve, edit any version, or reject.→ chat
  5. OutputReturn the notesReturn {{notes}}: the changelog entry to add to CHANGELOG.md or the GitHub release, and the other two to copy.→ file

Good for

Developers and product teams who ship from GitHub and want release notes, an in-app note and a short post from the same list of merged PRs.

Last reviewed

Skills this uses

  • release-notes-writer

    Turns merged pull requests or a commit log into release notes people want to read: groups changes into new, improved, fixed and breaking, drops internal-only work, describes what users can now do rather than how it was built, and gives migration steps for anything breaking. Offers a short social version too.

Install as a skill

The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “Release notes from merged PRs”.

Get the release-notes-from-merged-prs skill

What each step does

  1. 1. Paste the changes (Trigger)

    Start with {{changes}} for {{product}} {{version}}.

  2. 2. Sort and rewrite the changes (Skill)

    Loads the release-notes-writer skill.

    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.

  3. 3. Three versions (Parallel)

    Write your version for {{product}} {{version}} from {{grouped}} only. Leave out Internal items.

    • 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. 4. Check before publishing (Approval)

    Show {{notes}}. Approve, edit any version, or reject.

  5. 5. Return the notes (Output)

    Return {{notes}}: the changelog entry to add to CHANGELOG.md or the GitHub release, and the other two to copy.

Use it in your own agent

Fill in the inputs

PR titles and descriptions, or the output of git log <last-tag>..HEAD --merges.

Open in ClaudeOpen in ChatGPT3 inputs use their example until you fill them in.

Save as .claude/skills/release-notes-from-merged-prs/SKILL.md for Claude Code, or .agents/skills/release-notes-from-merged-prs/SKILL.md for Codex and other Agent Skills tools. Then ask: “run the Release notes from merged PRs workflow”.

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.

Want different steps? Open it in the workflow builder.