Release Notes

You know that painful translation layer between what shipped and what users actually need to hear? This handles it. Feed in JIRA tickets, PRs, or internal changelogs and it restructures everything into categorized release notes that lead with benefits instead of implementation details. It'll turn "Implemented Redis caching for dashboard endpoints" into "Dashboards load 3x faster." The format is sensible: new features, improvements, fixes, breaking changes, with tone adjustment for your audience. Saves the back-and-forth with product managers about what sounds too technical and what actually matters to the people reading your changelog.

skills.sh installs: 3.1K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill release-notes --agent claude-code

Installs into .claude/skills of the current project.

Files

Release Notes Generator

Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.

Context

You are writing release notes for $ARGUMENTS.

If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.

Instructions

Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
- What changed (feature, improvement, or fix)
- Who it affects (which user segment)
- Why it matters (the user benefit)
Categorize changes:
- New Features: Entirely new capabilities
- Improvements: Enhancements to existing features
- Bug Fixes: Issues resolved
- Breaking Changes: Anything that requires user action (migrations, API changes)
- Deprecations: Features being sunset