skills.rest
kochangbok
kochangbokCOMMUNITY
Explore all skills by this author →
GitHub

release-changelog

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

1|Updated Mar 29, 2026
Search Tags:#release management#versioning#commit analysis#GitHub API#changelog generation
One-click install
npx skills add https://github.com/kochangbok/paperclip-ko --skill release-changelog-kochangbok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/kochangbok/paperclip-ko/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/kochangbok/paperclip-ko --skill release-changelog-kochangbok

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the generation of the stable Paperclip release changelog, streamlining the process of compiling and presenting release notes.

Core Features & Use Cases

  • Changelog Generation: Automatically compile a changelog from commits, changesets, and merged pull requests.
  • Versioning Management: Utilizes calendar versioning for accurate release tracking.
  • Breaking Change Detection: Identifies and flags breaking changes for user awareness.
  • User-Friendly Format: Outputs a Markdown file formatted for easy review and inclusion in release documentation.

Quick Start

Run 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 merged pull requests and commits?▼

You generate a changelog from pull requests and commits by running a skill that analyzes Git history and merged pull requests via the GitHub API to automatically compile a Markdown changelog file.

How does breaking change detection work for release notes?▼

Breaking change detection for release notes works by analyzing commits and changesets to identify and flag breaking changes, ensuring users are aware of major impacts before the stable release.

Do I need Git and GitHub API access to automate changelog generation?▼

Yes, you need Git and GitHub API access to automate changelog generation, as the process requires retrieving commit data, changesets, and merged pull request information directly from the repository.

What is the best way to organize release notes using calendar versioning?▼

The best way to organize release notes using calendar versioning is to automate the compilation of commits and pull requests into a structured Markdown file that tracks releases accurately by date.

Can I output the changelog as a Markdown file for release documentation?▼

Yes, you can output the changelog as a Markdown file formatted for easy review and direct inclusion in your release documentation, streamlining the stable release publishing process.

Related Skills

Explore More Software Engineering Skills→
tamzitamzi

release-changelog

Generates stable Paperclip changelogs from Git commit history, GitHub pull requests, and Calab for versioning/release tracking.

Community
Advanced
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
xztxyxztxy
5

git-commit

Generate conventional commit messages with type, scope, and description.

Community
Basic
jhlee0409jhlee0409
7

afc:launch

Generate CHANGELOG entries, README updates, and GitHub release notes from git history.

Community
Intermediate