Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

release-notes — Claude Code skill: what it does, how to install

Creates user-facing release notes from tickets, PRDs, and changelogs. Use it when announcing updates or summarising shipped work.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add phuryn/pm-skills --skill release-notes -a claude-code
Open on GitHub

What release-notes does

The skill reads supplied tickets, PRDs, JIRA or Linear exports, Git logs, and internal changelogs. It sorts changes into new features, improvements, bug fixes, breaking changes, and deprecations, then turns them into plain-language release note entries without internal ticket references.

Entries lead with the user benefit and can follow a professional, friendly, or API-focused product voice. Provided visuals or screenshots are included. The output is saved as a Markdown document, with conversion to HTML or another format available on request.

When given a product URL, the skill uses web search to understand the product and audience. That is a reason to check whether web search is acceptable for the task.

What it helps with

  • turn tickets into release notes
  • group shipped changes by category
  • rewrite technical changes for users
  • describe breaking changes and required actions
  • convert Markdown notes to HTML

Example prompts for the agent

  • "Create user-facing release notes from these tickets."
  • "Summarise this PRD and Git log as a product update."
  • "Write release notes that cover breaking changes and deprecations."

How to install release-notes

1Skills CLI (Vercel)

npx skills add phuryn/pm-skills --skill release-notes -a claude-code

2Manually: put the files in place

~/.claude/skills/release-notes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release-notes/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Similar

scientific-writing K-Dense-AI This skill drafts and audits scientific manuscripts and reports while tying claims to verified evidence. Use it for sections, references, declarations, and submission checks. Claude Code CX Codex Cursor +1 2,400installs reference-list-builder Paramchoudhary This skill structures professional reference lists and drafts briefing materials for employment background checks. Claude Code CX Codex Cursor +1 9,300installs publish-to-pages official github Publishes presentations and HTML content to GitHub Pages by creating a repository and returning a live page address. Use it when files need to be shared as a web page. GitHub Copilot 1,800installs oo-component-documentation official github This skill creates or updates object-oriented component docs from code or an existing Markdown file. It helps keep new and revised documentation in one format. GitHub Copilot 1,800installs creating-oracle-to-postgres-migration-bug-report official github Creates structured bug reports for Oracle-to-PostgreSQL migration defects. Use it when a database behaviour difference needs a reproducible report with a cause and validation plan. GitHub Copilot 1,800installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. Claude Code Claude.ai 414,180installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs

Questions about release-notes

How do I install release-notes in Claude Code?

Run npx skills add phuryn/pm-skills --skill release-notes -a claude-code, then run npx skills add phuryn/pm-skills --skill release-notes -a claude-code again. The skill file is placed at ~/.claude/skills/release-notes/SKILL.md.

What does release-notes do?

It turns technical tickets, PRDs, and changelogs into release notes written for users. It categorises the changes and removes internal jargon and ticket references.

What output format does release-notes create?

It saves release notes as a Markdown document. It can convert the result to HTML or another format when requested.

Source text

SKILL.md · MIT 
---
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.

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

© phuryn · MIT · phuryn/pm-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor