skills.rest
seflless
sefllessCOMMUNITY
Explore all skills by this author →
𝕏@sefllessGitHub

update-release-notes

Aggregate merged PRs into next.mdx and archive release notes on new versions.

Updated Feb 6, 2026
Search Tags:#automation#changelog#documentation#github#release-notes#pr-automation
One-click install
npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill update-release-notes-seflless
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-release-notes
Source: https://github.com/seflless/tldraw-agent-claude-code-provider/tree/main/.claude/skills/update-release-notes
Command: npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill update-release-notes-seflless

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, bash, and includes scripts (resource) components.

What problem does it solve?

Update release notes automatically by aggregating merged PRs into the next release notes file, reducing manual toil and errors.

Core Features & Use Cases

  • Automatically update apps/docs/content/releases/next.mdx with new PR entries since the last release.
  • Archive next.mdx content to versioned releases when a new version is published, preserving historical notes.
  • Retrieve PR details in batches and categorize changes to keep release docs accurate and consistent.

Quick Start

Run the status script to identify new PRs and then update next.mdx with the latest changes.

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 is done by detecting new merges to main, retrieving PR details in batches, and categorizing changes into a centralized next.mdx file to reduce manual toil and errors.

How do I archive next.mdx release notes when publishing a new version?▼

Archiving next.mdx release notes on new versions involves moving the aggregated PR entries to a versioned releases directory, which preserves historical notes and synchronizes the main branch for the next release cycle.

Do I need GitHub CLI and jq to aggregate merged PRs into release notes?▼

Aggregating merged PRs into release notes requires GitHub CLI, jq, git, and bash to fetch PR details, parse JSON responses, interact with repositories, and execute the automation scripts.

What's the best way to keep centralized release docs synchronized with main?▼

Keeping centralized release docs synchronized with main is best handled by scripts that automatically detect new PRs merged since the last release and update the next.mdx file with structured change entries.

Can I categorize GitHub pull requests automatically for changelogs?▼

Categorizing GitHub pull requests automatically for changelogs is supported by fetching PR details in batches and mapping the structured data into the centralized releases directory documentation.

Does this approach work for projects without a centralized releases directory?▼

This approach for automating release notes does not work without a centralized releases directory, because the scripts specifically target the next.mdx file and depend on that structured publishing path.

Related Skills

Explore More Software Engineering Skills→
cedanlcedanl

release-notes

Draft Dutch release notes from merged PRs and closed issues.

Official
Advanced
tldrawtldraw
49.7k

update-release-notes

Automates updating next.mdx release notes with merged PR entries and archiving versions.

Official
Intermediate
dimagidimagi
3

release-notes

Summarize merged GitHub PRs between two releases into categorized Markdown notes.

Official
Advanced
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced