skills.rest
spandios
spandiosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-notes

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

Updated Feb 6, 2026
Search Tags:#changelog#summarization#technical writing#communication#release notes#product updates
One-click install
npx skills add https://github.com/spandios/vibe-utils --skill release-notes-spandios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/spandios/vibe-utils/tree/main/skills/release-notes
Command: npx skills add https://github.com/spandios/vibe-utils --skill release-notes-spandios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of user-facing release notes from technical documentation, saving time and ensuring clear communication of product updates.

Core Features & Use Cases

  • Summarize Changes: Transforms technical tickets, PRDs, or changelogs into clear, engaging summaries.
  • Categorize Updates: Organizes changes into New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations.
  • Use Case: Automatically generate the "What's New" section for your product's next release by feeding it a collection of JIRA tickets and pull request descriptions.

Quick Start

Use the release-notes skill to generate release notes for the new features described in the attached file 'feature-list.md'.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate user-facing release notes from raw changelogs and JIRA tickets?▼

You can generate user-facing release notes by feeding raw technical documentation like JIRA tickets, PRDs, or changelogs into the summarization process, which organizes changes into clear categories for your audience.

Can I categorize product updates into specific groups like new features and bug fixes?▼

Yes, product updates can be categorized automatically into predefined groups such as New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations to structure your communication clearly.

How does changelog summarization tailor technical writing for different product audiences?▼

Changelog summarization tailors technical writing by adjusting the tone and content format of the summarized product updates to match the specific audience reading the release notes.

What is the best way to automate creating a What's New section from pull request descriptions?▼

The best way to automate a What's New section is to process collections of pull request descriptions and technical tickets, transforming them into engaging summaries categorized by update type.

Do I need formatted input files to generate release notes for product updates?▼

No, you do not need strictly formatted input files; the system can process raw input such as plain text feature lists, PRDs, and changelogs to produce structured release notes.

Related Skills

Explore More Content & Communication Skills→
shalevaminshalevamin

release-notes

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

Community
Intermediate
qmuqmu
1

write-release-note

Generate structured release notes from branch story frontmatter to Markdown.

Official
Basic
patriot718patriot718

doc-coauthoring

Guide users through a structured co-authoring workflow for documentation.

Community
Advanced
MaVoid-TeamMaVoid-Team

release-notes

Convert tickets and changelogs into structured markdown release notes.

Official
Intermediate