Help us improve
Share bugs, ideas, or general feedback.
From pm-engineering
Converts git logs, commit lists, or release notes into polished changelogs following Keep a Changelog conventions. Categorizes changes and adds migration notes.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-engineeringHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-engineering:changelog-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Converts raw git commits, a diff summary, or developer release notes into a polished changelog entry — categorised, user-facing, and following Keep a Changelog conventions.
Generates user-friendly changelogs from git commit history by scanning, categorizing (features, fixes, etc.), filtering noise, and rephrasing technical details for customers.
Generates user-friendly changelogs from git commit history by categorizing changes and rephrasing technical details for releases, updates, and app stores.
Generates user-facing changelogs from git commits by categorizing changes and translating technical messages into customer-friendly release notes.
Share bugs, ideas, or general feedback.
Converts raw git commits, a diff summary, or developer release notes into a polished changelog entry — categorised, user-facing, and following Keep a Changelog conventions.
Ask for these if not provided:
git log --oneline, raw commit messages, or a description of what changed)Follow Keep a Changelog format:
[Only include if there are breaking changes]
Skill guidance — do not include the following section in the delivered changelog:
Language: Write for the reader, not the committer. "Add dark mode support" not "implement ThemeProvider with dark palette variant".
Breaking changes: Always call these out first with ⚠️. Include a migration path.
Bug fixes: Describe what was broken, not what was changed. "Fix crash when user has no profile picture" not "null-check avatar URL before rendering".
Granularity: Group related commits into one line. Don't list every micro-commit separately.
Tone: Active voice, imperative mood. "Add", "Fix", "Remove" — not "Added", "Fixed", "Removed".
Empty sections: Omit any section with no entries. Don't include empty ### Fixed blocks.