generating-release-noteslisted

Generates GitHub release notes from merged PRs and issues with automated categorization, breaking change detection, and optional upload via gh CLI. Use when creating releases, publishing new versions, documenting changes, preparing release notes, or when the user mentions "release notes", "changelog", "release", or "version announcement".
NASA-PDS/pds-agent-skills · ★ 1 · AI & Automation · score 67

Install: claude install-skill NASA-PDS/pds-agent-skills

# User-Friendly Release Notes (with Executive Summary + Links) ## Inputs - **repo**: GitHub org/repo (e.g., `NASA-PDS/doi-service`) - **tag/version**: e.g., `v1.6.0` - **date**: ISO or human date (e.g., `2025-11-05`) - **changes**: structured list of merged PRs/issues (title, labels, number, URL, author) - Each item SHOULD have: `title`, `labels[]`, `number`, `html_url`, and OPTIONAL `area`, `component`, `breaking`, `deprecation`, `security`, `runtime_requirements`, `upgrade_steps`, `impact`, `perf_metrics`. - **compare_url**: GitHub compare link for "Full changelog". - **upload (optional)**: boolean, if `true` upload the generated notes to GitHub release using `gh` CLI. - **compat_matrix (optional)**: component/version/requirements table for multi-component releases. - **known_issues (optional)**: items with link + workaround. - **docs_links (optional)**: docs, migration guide, artifacts, support channel. ## Prerequisites - For upload functionality: GitHub CLI (`gh`) must be installed and authenticated - Install: `brew install gh` (macOS) or see https://cli.github.com - Authenticate: `gh auth login` - Verify: `gh auth status` ## Output - Markdown formatted **Release Notes** with sections in this order (omit empties): 1) **⚠️ Breaking Changes** (ALWAYS FIRST if present; bold; clear impact statement + required migration steps; link) 2) **Highlights** (3–6 bullets, outcome-focused, each bullet ends with a link) 3) **New** 4) **Improvements** 5) **Fixes**