update-release-notes

Aggregate merged PRs into next.mdx and archive versioned release files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/arusinova/annarusinova-platform --skill update-release-notes-arusinova
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-release-notes
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/update-release-notes
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill update-release-notes-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, awk, grep, sed, tr, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the maintenance of release notes by aggregating merged PRs into the next release notes file and archiving releases when a new version is published, keeping documentation current with minimal manual effort.

Core Features & Use Cases

  • PR aggregation: collects merged PRs on main since the previous release and updates apps/docs/content/releases/next.mdx.
  • Archival workflow: creates a versioned release file (e.g., vX.Y.Z.mdx) and resets next.mdx to prepare for the next cycle.
  • PR detail integration: fetches PR metadata (title, author, labels, body) to populate release notes accurately.
  • Quality checks: ensures links, contributor credits, and formatting align with the release notes style guide.

Quick Start

Update the release notes by running the status script to generate a diff against the latest release and refresh next.mdx as new PRs are merged.

Frequently Asked Questions about update-release-notes

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

FAQPage Schema
How do I automate release notes from merged PRs?

Automating release notes from merged PRs involves fetching PR metadata like titles, authors, and labels to populate a next.mdx file. This Skill categorizes content according to your release notes style guide to keep documentation current.

What is the best way to generate a changelog from GitHub pull requests?

Generating a changelog from GitHub pull requests is best handled by diffing against the latest release and fetching merged PR data. This Skill automates that workflow, applying quality checks for links, contributor credits, and formatting alignment.

How do I archive release notes when publishing a new version?

Archiving release notes when publishing a new version requires creating a versioned file like vX.Y.Z.mdx and resetting the next.mdx file. This Skill implements this archival workflow automatically to prepare for the next release cycle.

Do I need GitHub CLI to aggregate PR data into documentation?

Aggregating PR data into documentation requires the GitHub CLI (gh) along with git, jq, awk, grep, sed, and tr. These dependencies are necessary to fetch PR metadata and process the diffing logic for your release notes.

How does PR aggregation handle formatting and contributor credits?

PR aggregation handles formatting and contributor credits by fetching detailed PR metadata and applying quality checks. This ensures links, author attributions, and content structure align with the established release notes style guide.