release-notes

Generate release notes from merged pull requests since the previous tag.

41|11|Updated May 22, 2025
One-click install
npx skills add https://github.com/receptron/mulmocast-app --skill release-notes-receptron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/receptron/mulmocast-app/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/receptron/mulmocast-app --skill release-notes-receptron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release notes often get written late or contain inaccurate summaries, because they are based on incomplete PR information instead of a full review of merged changes.

Core Features & Use Cases

  • Versioned release note generation: Creates release notes for a specific target version from changes merged since the previous release tag.
  • PR investigation and structured summarization: Collects PR numbers, dates, titles, bodies, labels, and related files, then produces both PR summaries and user-facing release notes.
  • Upstream model-change verification: When the upstream mulmocast package is updated, diffs actual code to distinguish models that are truly new versus those already present in the prior version.
  • Clear user vs developer impact categorization: Separates user-visible fixes and improvements from developer-only/internal changes for appropriate sections.

Quick Start

Generate the release notes by providing the target version number (for example, 1.0.11) and letting the skill compile PR summaries and user-facing notes into docs/release_notes/v1.0.11/.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate app release notes from merged pull requests?

You can automatically generate release notes by collecting and summarizing all merged pull requests since your previous release tag, categorizing changes by user impact, and outputting structured documentation to a versioned directory.

What's the best way to summarize GitHub PR history for changelog documentation?

The best approach collects PR numbers, dates, titles, bodies, and labels via GitHub gh commands, then structures the changelog by separating user-visible fixes and improvements from developer-only internal changes.

How can I verify upstream dependency updates in release notes using code diff validation?

Verify upstream dependency updates by running code diff validation against the prior version to distinguish models that are truly new from those already present, ensuring release notes avoid speculative descriptions not supported by actual PR summaries.

Do I need a version argument to generate versioned release notes for my app?

Yes, providing a specific target version argument is required to scope PR discovery and output the generated release notes into a structured directory path like docs/release_notes/v<version>.

Does release note generation work with GitHub tags and gh commands?

Yes, the workflow relies on GitHub release tags and gh commands to discover merged pull requests, collect related file metadata, and compile structured PR summaries and user-facing release notes.

Why should release notes avoid speculative descriptions not supported by PR summaries?

Avoiding speculative descriptions not supported by PR summaries prevents inaccurate changelog entries, ensuring release notes strictly reflect actual merged code changes and verified user impact rather than assumptions.