Release Notes

Name: Release Notes
Author: phuryn

phuryn/pm-skills

2.1k installs
24.9k repo stars
Updated July 3, 2026
phuryn/pm-skills

release-notes is an agent skill for Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing

About

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped. The release-notes skill documents workflows and patterns from the repository SKILL.md. --- name: release-notes description: "Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped." --- ## 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. **Gather raw material**: Read all provided tickets, changelogs, or descriptions.

**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**:

Release Notes by the numbers

2,060 all-time installs (skills.sh)
+85 installs in the week ending Aug 5, 2026 (Skillselion tracking)
Ranked #180 of 1,879 Documentation skills by installs in the Skillselion catalog
Security screen: MEDIUM risk (skills.sh audit)
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

release-notes capabilities & compatibility

Capabilities: **gather raw material**: read all provided ticke · what changed (feature, improvement, or fix) · who it affects (which user segment) · why it matters (the user benefit) · **categorize changes**:
Use cases: documentation

From the docs

What release-notes says it does

--- name: release-notes description: "Generate user-facing release notes from tickets, PRDs, or changelogs.

SKILL.md

Creates clear, engaging summaries organized by category (new features, improvements, fixes).

SKILL.md

### Context You are writing release notes for **$ARGUMENTS**.

SKILL.md

If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first.

SKILL.md

npx skills add https://github.com/phuryn/pm-skills --skill release-notes

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/phuryn/pm-skills/release-notes.svg)](https://skillselion.com/skills/phuryn/pm-skills/release-notes)

Installs	2.1k
repo stars	★ 24.9k
Security audit	2 / 3 scanners passed
Last updated	July 3, 2026
Repository	phuryn/pm-skills ↗

What problem does release-notes solve for developers using the documented workflows?

Who is it for?

Developers working with release-notes patterns described in the skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill documented scope.

When should I use this skill?

What you get

Grounded guidance and workflows from SKILL.md for release-notes.

Categorized release-note document
User-facing changelog copy

Files

SKILL.mdMarkdownGitHub ↗

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

1. 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)

2. 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

3. Write each entry following these principles:

Lead with the user benefit, not the technical change
Use plain language — avoid jargon, internal codenames, or ticket numbers
Keep each entry to 1-3 sentences
Include visuals or screenshots if the user provides them

Example transformations:

Technical: "Implemented Redis caching layer for dashboard API endpoints"
User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."

Technical: "Fixed race condition in concurrent checkout flow"
User-facing: "Fixed an issue where some orders could fail during high-traffic periods."

4. Structure the release notes:

   # [Product Name] — [Version / Date]

   ## New Features
   - **[Feature name]**: [1-2 sentence description of what it does and why it matters]

   ## Improvements
   - **[Area]**: [What got better and how it helps]

   ## Bug Fixes
   - Fixed [issue description in user terms]

   ## Breaking Changes (if any)
   - **Action required**: [What users need to do]

5. Adjust tone to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.

Save as a markdown document. If the user wants HTML or another format, convert accordingly.