Release Changelog

Generates a user-facing changelog for stable Paperclip releases by reading commits, changesets, and merged PRs since the last tag, then organizing them into breaking changes, highlights, improvements, and fixes. Built for calendar versioning, not semver. It's idempotent (checks if the file exists first), knows to exclude canary releases from the filename, and pulls contributor attribution from merge commits and GitHub usernames. The skill won't overwrite existing changelogs without asking and always presents a draft for review before you ship. If your project uses calver and you're tired of manually sorting through git history to write release notes, this handles the archaeology and formatting.

skills.sh installs: 298
GitHub stars: 112.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add paperclipai/paperclip --skill release-changelog --agent claude-code

Installs into .claude/skills of the current project.

Files

Release Changelog Skill

Generate the user-facing changelog for the stable Paperclip release.

Versioning Model

Paperclip uses calendar versioning (calver):

Stable releases: YYYY.MDD.P (e.g. 2026.318.0)
Canary releases: YYYY.MDD.P-canary.N (e.g. 2026.318.1-canary.0)
Git tags: vYYYY.MDD.P for stable, canary/vYYYY.MDD.P-canary.N for canary

There are no major/minor/patch bumps. The stable version is derived from the intended release date (UTC) plus the next same-day stable patch slot.

Output:

releases/vYYYY.MDD.P.md
a release Case, upserted by (caseType, key) when Cases are enabled, with a body document revision containing the changelog body

Important rules:

even if there are canary releases such as 2026.318.1-canary.0, the changelog file stays releases/v2026.318.1.md
do not derive versions from semver bump types
do not create canary changelog files