changelog · pipecat-ai — Claude Code skill: generate release notes from PR commits
Skill that builds changelog files for meaningful commits in a pull request.
BSD-2-Clause ★ 17,367 updated 2026-10-29
npx skills add pipecat-ai/pipecat --skill changelog -a claude-codeWhat changelog does
The skill keeps your project's history current without manual work. It reviews commits, skips tests and refactoring, then writes files to changelog/ with the format {PR_NUMBER}.{type}.md. Each file starts with - followed by a description, and can include indented details or code examples below.
Entries prioritize what developers working with the framework will notice: new APIs, behaviour changes, fixed bugs they might have hit. Implementation details come second. Eight entry types are supported: added, changed, deprecated, removed, fixed, security, performance, other. Breaking changes get a ⚠️ prefix.
Once entries are written, the skill runs prose-review changelog/ to check tone and clarity, ensuring each note is concise and accessible.
What it helps with
- categorise PR commits by change type
- write structured changelog entries
- separate user-visible changes from internal refactoring
- mark breaking changes with a warning symbol
- review style and readability of entries
Example prompts for the agent
- Generate changelog files for PR 3519 based on commits in the current branch
- Create two entries: a new feature in added and a bug fix in fixed
- Build changelog for this pull request and check the style of each entry
How to install changelog
1Skills CLI (Vercel)
npx skills add pipecat-ai/pipecat --skill changelog -a claude-code2Manually: put the files in place
~/.claude/skills/changelog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/changelog/
1Skills CLI (Vercel)
npx skills add pipecat-ai/pipecat --skill changelog -a codex2Manually: put the files in place
.agents/skills/changelog/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pipecat-ai/pipecat --skill changelog -a cursor2Manually: put the files in place
.cursor/skills/changelog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pipecat-ai/pipecat .claude/skills/changelog2Manually: put the files in place
.github/skills/changelog/SKILL.md1Skills CLI (Vercel)
npx skills add pipecat-ai/pipecat --skill changelog -a gemini-cli2Platform CLI
gemini skills install https://github.com/pipecat-ai/pipecat --path .claude/skills/changelogManually: put the files in place
.devin/skills/changelog/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pipecat-ai/pipecat --skill changelog -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about changelog
How do I install changelog in Claude Code?
Run npx skills add pipecat-ai/pipecat --skill changelog -a claude-code, then find the skill file at ~/.claude/skills/changelog/SKILL.md.
What does the changelog skill do?
It reviews commits on your branch, filters out documentation and tests, then creates files in changelog/ with descriptions of each change grouped by type: new features, fixes, removals, performance work, and more.
What entry types does changelog support?
Eight types: added for new features, changed for modifications, deprecated for deprecated items, removed for deletions, fixed for bug fixes, security for security updates, performance for optimizations, other for miscellaneous changes. Breaking changes use a ⚠️ prefix.
Source text
SKILL.md · BSD-2-Clause
---
name: changelog
description: Create changelog files for important commits in a PR
---
Create changelog files for the important commits in this PR. The PR number is provided as an argument.
## Instructions
1. Skip changelog for: documentation-only, internal refactoring, test-only, CI changes, and fixes to changes that have not shipped yet (the unreleased change's entry covers them — update that entry instead if the fix alters what it should say).
2. First, check what commits are on the current branch compared to main:
```
git log main..HEAD --oneline
```
3. For each significant change, create a changelog file in the `changelog/` folder using the format:
Allowed types: `added`, `changed`, `deprecated`, `removed`, `fixed`, `security`, `performance`, `other`
- `{PR_NUMBER}.added.md` - for new features
- `{PR_NUMBER}.added.2.md`, `{PR_NUMBER}.added.3.md` - for additional entries of the same type
- `{PR_NUMBER}.changed.md` - for changes to existing functionality
- `{PR_NUMBER}.fixed.md` - for bug fixes
- `{PR_NUMBER}.deprecated.md` - for deprecations
- `{PR_NUMBER}.removed.md` - for removed features
- `{PR_NUMBER}.security.md` - for security fixes
- `{PR_NUMBER}.performance.md` - for performance improvements
- `{PR_NUMBER}.other.md` - for other changes
4. Each changelog file should at least contain a main single line starting with `- ` followed by a clear description of the change. No line wrapping.
5. If the change is complicated, changelog files can have indented lines after the main line with additional details or code samples.
6. Use ⚠️ emoji prefix for breaking changes.
7. **Write changes in user-facing terms first.** Lead with what users of the framework will notice: new APIs, changed behavior, new parameters, fixed bugs they might have hit, etc. Implementation details (internal refactoring, how something is wired up under the hood) can be included as secondary context after the user-facing description, but should never be the *only* content of a changelog entry when there is a user-visible effect.
**Good** (user-facing first, implementation detail as context):
```
- Turn completion instructions now persist correctly across full context updates when using `system_instruction`. Previously they were injected as a context system message, which caused warning spam and didn't survive context updates.
```
**Bad** (implementation detail only, no user-facing framing):
```
- Fixed turn completion instructions being injected as a context system message instead of using `system_instruction`.
```
Ask yourself: "If I'm a developer building on Pipecat, what would I notice changed?" Start there.
8. Once the entries are written, run `/prose-review changelog/` and fix anything it flags.
## Example
For PR #3519 with a new feature and a bug fix:
`changelog/3519.added.md`:
```
- Added `SomeNewFeature` for doing something useful.
```
`changelog/3519.fixed.md`:
```
- Fixed an issue where something was not working correctly in some user-visible scenario. The root cause was an internal implementation detail.
```
© pipecat-ai · BSD-2-Clause · pipecat-ai/pipecat
Similar skills
All skills for Code review and refactoring →changelog by other authors comes first.