release-notes

Generate user-facing release notes from tickets, PRDs, and changelogs.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill release-notes-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/moonzff/Codex_up/tree/main/skills/product-planning/release-notes
Command: npx skills add https://github.com/moonzff/Codex_up --skill release-notes-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical tickets, PRDs, and internal changelogs are written for engineers, not users. This Skill transforms that raw material into polished, user-facing release notes that lead with benefits instead of implementation details. ## Core Features & Use Cases - Automatic Categorization: Organizes changes into New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations. - Benefit-First Rewriting: Converts technical jargon (e.g., "Redis caching layer") into plain user value (e.g., "Dashboards load up to 3x faster"). - Tone Adaptation: Adjusts voice for B2B, consumer, or developer/API audiences. - Use Case: Paste a sprint's JIRA export or git log, and receive a structured markdown release notes document ready to publish or convert to HTML. ## Quick Start Ask the assistant to generate release notes from your attached changelog, ticket export, or PRD, specifying the product name and version or date.

Frequently Asked Questions about release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write release notes from JIRA tickets?▼

Provide the JIRA export or ticket list as input, and the Skill extracts what changed, who it affects, and why it matters. It then categorizes entries and rewrites them as benefit-led, jargon-free summaries organized by change type.

How to convert a technical changelog into user-facing release notes?▼

Paste the internal changelog or git log and the Skill translates each technical entry into plain language focused on user benefit. For example, "fixed race condition in checkout" becomes "fixed an issue where orders could fail during high-traffic periods."

What categories should release notes include?▼

The Skill organizes entries into New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations. Breaking changes are flagged with explicit action-required notes so users know what steps they must take.

Can release notes be generated in HTML instead of markdown?▼

Yes. The default output is a structured markdown document, but the Skill converts to HTML or other formats on request. Just specify the desired output format when making the request.

What inputs does the release notes generator accept?▼

It accepts JIRA exports, Linear tickets, PRDs, git logs, and internal changelogs as source material. If a product URL is mentioned, web research can be used to understand the product and its audience.