changelog-for-humans
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
npx skills add mohitagw15856/pm-claude-skills --skill changelog-for-humans --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 For Humans Skill Commit lists are what happened; changelogs are *what it means for you* — and most teams publish the former with headers. The human version translates each change into its so-what ("Faster search" → "Search results now return in under a second on large workspaces"), orders by reader impact — breaking changes first with migration steps, improvements second, internal plumbing compressed to a line — and never buries the one thing users must do behind twelve things the team is proud of. When audiences diverge (end users vs. developers), the changelog splits rather than serving both badly. ## What This Skill Produces - **The impact-grouped changelog** — ⚠ breaking/action-needed → ✨ new & improved → 🔧 fixes → (plumbing, one line) - **The so-what translations** — each entry: what changed *for the reader*, not what the team did - **The breaking block** — who's affected, what breaks, the migration steps, the deadline if one exists - **The audience split** — the user-facing notes and the developer/API notes, separated when their so-whats differ ## Required Inputs Ask for these if not provided: - **The raw changes** — commits, PR titles, the team's list; translati
- What This Skill Produces
- Required Inputs
- Framework: The Translation Rules
- Output Format
- ⚠ Action needed
- ✨ New & improved
- 🔧 Fixed
- Quality Checks
- Anti-Patterns
What does the changelog-for-humans skill do?
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill changelog-for-humans --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.