Guide · Agent skill
How to use the Release Notes Generator agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Release Notes Generator is an agent skill from the pm-skills collection that teaches an AI agent how to turn raw product material into polished, user-facing release notes. This guide is for product managers, developers, founders and marketers who want a changelog or ticket list rewritten for customers. By the end you will know what the skill does, how to install it, how to ask for it, and where its output needs a human check.
Release Notes Generatorphuryn/pm-skills · MIT Download the skill Quick start
- 1Download the ZIP. Download the release-notes skill ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Gather your source material. Collect the tickets, PRDs, Git logs or changelog text you want included.
- 5Ask in plain language. Request release notes or a changelog for your product and audience, and attach the material.
- 6Review the draft. Check each benefit against the source, and confirm breaking changes and deprecations.
What is an agent skill and what does this one do?
An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when a task matches the skill's description. This one is named release-notes and is described as generating user-facing release notes from tickets, PRDs, or changelogs.
Given raw material such as Jira or Linear tickets, product requirement docs, Git logs or internal changelogs, the agent rewrites each change in plain, benefit-focused language. It sorts entries into New Features, Improvements, Bug Fixes, Breaking Changes and Deprecations, and it adjusts tone for B2B, consumer or developer audiences.
- Reads the provided tickets, changelogs or descriptions and extracts what changed, who it affects and why it matters.
- Leads each entry with the user benefit and removes ticket numbers, internal codenames and jargon.
- Keeps each entry to 1-3 sentences.
- Saves the result as a markdown document, or converts it to HTML or another format on request.
Install the release-notes skill
Download the ZIP file from this page. Then choose one of the two install routes below.
For Claude Code, unzip the file into your personal skills folder at ~/.claude/skills/ so the skill is available in every project. To limit it to one project, unzip it into that project's .claude/skills/ folder instead.
In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
- Personal (all projects): unzip into ~/.claude/skills/
- Single project: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
What does the skill need before you start?
The skill's metadata lists no required tools, packages or accounts. It does not run scripts and does not use the network by itself. The only file included is SKILL.md.
The quality of the output depends on the input. Give the agent the actual tickets, PRDs, Git logs or changelog text you want covered. The skill's instructions say that if you mention a product URL, the agent may use web search to understand the product and audience, so that step only happens when you ask for it.
How do you trigger the skill with a natural request?
You do not need a special command. Describe the job in plain words that match the skill's purpose, such as writing release notes, creating a changelog, announcing product updates or summarizing what shipped. Attach or paste the source material in the same message.
The skill's context section refers to the product you are writing for, so name the product and the audience where you can.
- Write release notes for [product] version [X] from these Jira tickets: [paste or attach export]
- Turn this Git log into a customer-facing changelog for a B2B audience.
- Summarize what shipped this sprint for our consumer app users, using these Linear tickets.
- Draft an announcement for our developers from this internal changelog, focused on the API changes.
What does the output look like?
The skill gives the agent a standard markdown layout. Each category becomes a heading, and each entry is a short bullet. Breaking changes are flagged with a clear action note so readers know what they must do.
The skill also includes example rewrites that show the difference between a technical line and a user-facing line, for instance turning a caching change into a note about dashboards loading faster.
# [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]What safety and review points should you know?
The output is drafted by an AI and still needs human review before it reaches customers. This skill is not suited to exact, legally reviewed compliance or security disclosures.
Vague or missing tickets are the main risk. The agent may infer a benefit that did not actually ship, so check every claim against the source material before publishing.
- Review each benefit statement against the ticket or PRD it came from.
- Confirm breaking changes and deprecations manually, since users act on them.
- Do not use the output as a security advisory or legal notice without expert review.
Tips for better release notes
Feed the agent complete material. Ticket titles alone rarely explain the user benefit, so include the description or PRD section where possible.
State the audience and voice up front. The skill adjusts tone for B2B, consumer or developer readers, so say which one applies.
- Group related tickets into one entry when they serve the same user goal.
- Ask for HTML or another format if your publishing tool needs it; the skill allows conversion.
- Keep a human editor in the loop for the final wording.
What people use it for
- Turning a sprint's Jira or Linear tickets into a customer email announcing new features.
- Converting a Git log into a readable changelog for a developer-facing API.
- Drafting a product update post for marketing from internal PRD documentation.
- Summarizing what shipped for a team's stakeholders in plain language.
Frequently asked questions
How do I install the release-notes agent skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ to use it in all projects, or into a project's .claude/skills/ folder for one project. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
Does the release-notes skill cost anything or have a licence?
The skill is listed under the MIT licence. Check the repository's licence file for the full terms before reusing it.
What does the release-notes skill require?
The metadata lists no required tools or accounts. It does not run scripts and does not use the network on its own. Your main requirement is the source material you want turned into notes.
Can it write release notes from Jira or Linear tickets?
Yes. The skill is designed to read Jira or Linear exports, PRDs, Git logs and internal changelogs, then rewrite them as customer-facing notes.
Is it safe to publish the output without checking it?
No. The output is AI-drafted and needs human review, especially for breaking changes and any claims about what shipped. It is not suitable for exact, legally reviewed compliance or security disclosures.
What should I use instead if I need a legally reviewed disclosure?
Use a process that involves legal or security review from the start. This skill helps draft plain-language notes, but it does not replace expert sign-off on compliance or security wording.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a product manager, developer, founder or marketer who needs readable release notes from tickets, PRDs or changelogs and can review the draft. Pick something else if you need exact, legally reviewed compliance or security disclosures, or if your source tickets are too vague to confirm what actually shipped.
Download the skill