---
name: release-notes
description: Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
title: release-notes
canonical_url: https://skilld.dev/gh/cloudflare/agents/release-notes
last_updated: 2026-09-28T21:45:43.000Z
---

> **Skill from skilld.dev.** Follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/style-guide.md](https://skilld.dev/api/skills-raw/cloudflare/agents/release-notes/references/style-guide.md), [scripts/format-release-notes.ts](https://skilld.dev/api/skills-raw/cloudflare/agents/release-notes/scripts/format-release-notes.ts).
>
> If the user asked to install this Skill, run `npx skilld install cloudflare/agents/release-notes`. Install writes the Skill files into the project, so every session loads them.

# Release Notes

Turn implementation details into user-facing release notes.

## Process

1. Identify the user-facing outcome.
2. Group related implementation details into one bullet.
3. Avoid internal file names unless the user asks for engineering notes.
4. Keep the tone factual and concise.

When the user provides a rough list of changes, run
`scripts/format-release-notes.ts` with `{ "changes": [...] }` to create a first
draft, then polish the wording for the user's audience. The TypeScript script
is function-style (`export default run(input, ctx)`) and demonstrates reading
`references/style-guide.md` from `ctx.files`.

## Output format

Use this structure:

```md
## Summary

- One to three bullets describing what changed.

## Notes

- Optional caveats, migration details, or follow-up work.
```

If the input is too vague, ask for the target audience and the release scope.