# Release Notes

> Assemble release notes for a billing-api tag from merged pull requests. Use when cutting a release or when asked what shipped in a version.

- Skill: `stbenjam/release-notes-5` (Agent Skill)
- Install (CLI): `npx skillmds@latest add stbenjam/release-notes-5`
- Raw SKILL.md: https://api.skillmd.com/api/skills/stbenjam/release-notes-5/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: stbenjam (https://skillmd.com/u/stbenjam)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/stbenjam/release-notes-5

---


# Release notes

Assemble the notes for one tag from the pull requests merged since the
previous tag.

## Gather the changes

1. Find the previous tag with `git describe --tags --abbrev=0 HEAD^`.
2. List the merges with `git log --merges --pretty=%s <previous>..HEAD`.
3. For each merge, read the pull request body with
   `gh pr view <number> --json title,body`.

## Write the notes

Group the entries under three headings, in this order: `Added`, `Changed`,
`Fixed`. Drop a heading with no entries rather than writing "none".

Write each entry as one sentence in the past tense, naming the behaviour a
user sees rather than the code that changed. Append the issue key in
parentheses.

## Finish

Write the result to `docs/releases/<tag>.md` and stop. Do not tag, commit,
or publish anything.