Stats
Actions
Tags
From release
Generate or update CHANGELOG.md from git commits since the last tag. Use when the user asks to "update the changelog", "write a changelog entry", "document changes", or needs to record changes for a release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/release:changelogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a changelog entry from git history and update CHANGELOG.md.
Generate a changelog entry from git history and update CHANGELOG.md.
git tag --list --sort=-v:refname<latest-tag>..HEAD.git log <range> --onelineRead CHANGELOG.md if it exists. Match the project's existing format.
If no changelog exists, use Keep a Changelog format with these sections:
Map conventional commit prefixes to changelog sections:
feat: to Addedfix: to Fixedrefactor:, perf: to Changeddocs:, test:, ci:, chore:, style: to omitted (unless they have user-facing impact)BREAKING CHANGE or ! marker to a prominent note at the top of the entryFor non-conventional commits, categorize by the change description.
Draft the entry with:
Present the draft in a codeblock for review. Do not write to the file until the developer confirms.
Prepend the confirmed entry to CHANGELOG.md, below the header and above the previous version entry.
git tag or git push.npx claudepluginhub znorris/claude-marketplace --plugin releaseGenerates a formatted CHANGELOG.md from git commit history, grouped by type and ready for release.
Generates or refreshes CHANGELOG.md from conventional git commits in Keep a Changelog format. Incremental mode appends new commits; --from-scratch regenerates from tags/full history.
Analyzes git commit history to generate changelogs with semantic versioning, conventional commit categorization, and formats like Keep a Changelog, Conventional, or GitHub. Use for CHANGELOG.md updates, release notes, and version bumps.