release-changelog

Generate stable release changelogs from git commits, changesets, and merged pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/papertapeai/papertape --skill release-changelog-papertapeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/papertapeai/papertape/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/papertapeai/papertape --skill release-changelog-papertapeai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of user-facing changelogs for stable software releases, ensuring consistency and saving developers time.

Core Features & Use Cases

  • Automated Changelog Generation: Reads commits, changesets, and PRs to compile a changelog.
  • Breaking Change Detection: Identifies and flags breaking changes for user awareness.
  • Categorization: Organizes changes into predefined sections like 'Breaking Changes', 'Highlights', 'Improvements', and 'Fixes'.
  • Contributor Attribution: Automatically includes GitHub usernames for all contributors.
  • Use Case: Before releasing a new version of Papertape, this Skill can be invoked to draft the releases/vX.Y.Z.md file, which is then reviewed and approved by the release manager.

Quick Start

Use the release-changelog skill to generate the changelog for the next stable release.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I generate a changelog from git commits and pull requests?

Generate a changelog by analyzing git commits, changesets, and merged pull requests since the last stable tag. The skill automatically detects breaking changes, categorizes updates into user-facing sections, and attributes contributions via GitHub usernames.

Can I automatically detect breaking changes for release notes?

Yes, automated breaking change detection is built into release notes generation. The skill analyzes your git history and changesets to identify and flag breaking changes, ensuring users are aware of potential migration issues.

How do I categorize release notes into sections like improvements and fixes?

Categorize release notes by organizing changes into predefined sections such as Breaking Changes, Highlights, Improvements, and Fixes. This automated categorization reads your commit history and PRs to structure the final changelog.

What is the best way to attribute GitHub contributors in a changelog?

Attribute GitHub contributors in a changelog by automatically extracting and mapping GitHub usernames from merged pull requests. This ensures all contributors are properly credited in the generated release notes.

Will the changelog generation overwrite an existing changelog file?

No, changelog generation ensures idempotency by checking for existing changelog files before regeneration. This prevents accidental overwrites, and the generated artifact is always prepared for human review prior to release.

How do I draft a version release file for human review?

Draft a version release file by invoking the skill to compile a draft changelog, such as a releases/vX.Y.Z.md file. The generated artifact is then reviewed and approved by the release manager before publishing.