Claude Code Changelog Skill for Pipecat Pull Requests
Create separate release-note fragments for user-visible Pipecat changes. The skill classifies each feature or fix and names its Markdown fragment using the pull-request number.
中文Install in Claude Code
Use Claude Code in the pinned Pipecat checkout. Have the working branch, its main baseline, and the pull-request number ready.
- Confirm `.claude/skills/changelog/SKILL.md` is present in the pinned Pipecat checkout.
- Start Claude Code at the repository root and call `/changelog` with the PR number. Keep the repository's `prose-review` skill for the final wording check.
Example task
Suppose PR #4107 introduces a caption-color option, fixes missing captions after reconnect, and adds tests. Ask for one fragment per user-visible change and put the effect on framework users first.What to check
Expect `4107.added.md` and `4107.fixed.md` for the option and reconnection fix. No separate entry is needed for the test-only change.
Original SKILL.md on GitHub · Updated
Frequently asked question
How are two added features in one Pipecat PR named?
Use `<PR>.added.md` for the first fragment and `<PR>.added.2.md` or `<PR>.added.3.md` for additional ones. Start each file with the change a user can observe.