generating-release-notes

Generate GitHub release notes from merged PRs and issues with automated categorization.

1|1|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/NASA-PDS/pds-agent-skills --skill generating-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-release-notes
Source: https://github.com/NASA-PDS/pds-agent-skills/tree/main/generating-release-notes
Command: npx skills add https://github.com/NASA-PDS/pds-agent-skills --skill generating-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub release notes are time-consuming to assemble; this skill automates the process by aggregating merged PRs and issues, applying automated categorization, detecting breaking changes, and optionally uploading the notes to a GitHub release.

Core Features & Use Cases

  • Automatic categorization of changes into New, Improvements, Fixes, Security, and Breaking Changes.
  • Breaking-change detection to surface structural and compatibility impacts.
  • Optional upload via gh CLI to publish the release notes alongside a GitHub release.
  • Use cases include preparing release notes for software versions, changelogs, and version announcements.

Quick Start

Provide the repo, tag/version, date, and changes input to generate release notes.

Frequently Asked Questions about generating-release-notes

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

FAQPage Schema
How do I automatically generate GitHub release notes from merged PRs?

Automating GitHub release notes from merged PRs is done by aggregating pull requests and issues, then applying automated categorization into changes, fixes, and breaking impacts. Provide the repo, tag, and date inputs to generate the notes.

Can I use the gh CLI to upload release notes directly to GitHub?

Yes, you can use the gh CLI to upload release notes directly to GitHub. This skill optionally publishes the generated notes alongside a GitHub release using the gh CLI command line interface after composition.

What is automated breaking-change detection in release notes?

Automated breaking-change detection in release notes surfaces structural and compatibility impacts from merged changes. It categorizes these impacts separately so developers can quickly identify compatibility risks before version announcements.

How are merged pull requests categorized into changelogs?

Merged pull requests are categorized into changelogs by sorting changes into New, Improvements, Fixes, Security, and Breaking Changes. This automated categorization organizes raw pull request data into structured release notes.

What inputs do I need to prepare release notes for a software version?

To prepare release notes for a software version, you need to provide the repo, tag or version, date, changes, and an optional compare URL. These inputs compose comprehensive changelogs and version announcements.