ywc-changelog-release-notes

Name: ywc-changelog-release-notes
Availability: InStock
Author: yongwoon

Generate CHANGELOG.md entries and release notes from git history and merged pull requests.

8|1|Updated May 13, 2026

Search Tags:#automation #git #changelog #documentation #release notes #pull requests

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-changelog-release-notes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-changelog-release-notes
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-changelog-release-notes
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-changelog-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates the manual effort and inconsistency involved in documenting software releases, ensuring that both developers and end-users receive clear, accurate, and well-formatted information.

Core Features & Use Cases

Dual-Output Generation: Automatically produces a technical CHANGELOG.md for developers and a plain-language summary for end-users.
Intelligent Parsing: Analyzes git history, merged PRs, or custom PR lists to categorize changes into Added, Fixed, Security, and more.
Use Case: Before tagging a new version, use this skill to generate a professional release summary and a Keep a Changelog-compliant entry, ensuring all security patches and features are documented without manual drafting.

Quick Start

Use the ywc-changelog-release-notes skill to generate both the developer changelog and user-facing release notes for version 1.2.0.

Frequently Asked Questions about ywc-changelog-release-notes

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

FAQPage Schema

How do I generate release notes from git history and merged pull requests?▼

You can generate release notes by parsing git history and merged pull requests to automatically categorize commits into technical CHANGELOG.md entries and plain-language summaries for end-users using conventional commit standards.

What is the best way to automate a changelog for both developers and end-users?▼

Automating a changelog with dual-output generation produces a technical CHANGELOG.md for developers alongside a plain-language summary for end-users, ensuring both audiences receive clear and well-formatted release information without manual drafting.

Does this changelog generation method require the GitHub CLI?▼

Yes, this method requires the GitHub CLI to fetch pull request metadata and enrich the generated documentation with security vulnerability references and PR details from your repository.

Can I categorize git commits into Added, Fixed, and Security sections automatically?▼

Yes, intelligent parsing analyzes git history and merged PRs to automatically categorize commits into Added, Fixed, Security, and other sections based on conventional commit standards.

When do I need a Keep a Changelog-compliant entry for my software release?▼

You need a Keep a Changelog-compliant entry before tagging a new version to ensure all security patches and features are professionally documented without manual drafting, providing clear release information to both developers and users.