changelog-writer
Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.
npx skills add mohitagw15856/pm-claude-skills --skill changelog-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Changelog Writer Skill Raw commit logs are written for the author; a changelog is written for the *user*. This skill turns a pile of commits/PRs/changes into a clean release entry — grouped by type, in plain user-facing language, with **breaking changes and upgrade steps surfaced first** so nobody gets surprised. ## Required Inputs Ask for these only if they aren't already provided: - **The changes** — commit messages, PR titles, or a bullet list of what changed. - **Version & date** — the release number (or help pick per semver) and date. - **Audience** — end users, API consumers, library developers (sets the voice). - **Conventions** (optional) — Keep a Changelog, an existing style, links to issues/PRs. ## Output Format Follow [Keep a Changelog](https://keepachangelog.com) conventions: ### [version] — [date] **⚠️ Breaking changes** (only if any) — each breaking change + the **exact migration step** to fix it. This goes first. **Added** — new features/capabilities, in user terms. **Changed** — changes to existing behavior. **Deprecated** — soon-to-be-removed features (and what to use instead). **Fixed** — bug fixes (what was broken, from the user's view). **Security** — any secu
- Required Inputs
- Output Format
- [version] — [date]
- Quality Checks
- Anti-Patterns
- Based On
What does the changelog-writer skill do?
Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.