GitHub Changelog

Generate changelogs from merged pull requests and commits using GitHub CLI.

1|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/dtsong/claude-code-windows-setup --skill github-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub Changelog
Source: https://github.com/dtsong/claude-code-windows-setup/tree/main/skills/github-workflow/skills/gh-changelog
Command: npx skills add https://github.com/dtsong/claude-code-windows-setup --skill github-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of changelogs by analyzing merged pull requests and commits, streamlining the release notes process.

Core Features & Use Cases

  • Automated Changelog Generation: Creates release notes based on Git history since the last tag or a specified version.
  • Flexible Formatting: Supports Markdown and JSON output formats.
  • Categorization: Organizes changes into Features, Bug Fixes, Performance improvements, Documentation updates, and Breaking Changes based on PR labels or conventional commits.
  • Use Case: After merging several features and bug fixes, use this Skill to quickly generate a draft of your release notes for the next version.

Quick Start

Generate a changelog for the current release using the gh-changelog skill.

Frequently Asked Questions about GitHub Changelog

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

FAQPage Schema
How do I generate a changelog from Git history automatically?

You can generate a changelog from Git history automatically by analyzing merged pull requests and commits. This skill processes repository history via GitHub CLI to format release notes for specified version ranges.

Can I format release notes as JSON instead of Markdown?

Yes, you can format release notes as JSON instead of Markdown. This changelog generation skill supports flexible formatting, allowing you to output your categorized release notes in either Markdown or JSON format.

How do I categorize changes in release notes using conventional commits?

To categorize changes in release notes using conventional commits, the tool parses commit messages and PR labels. It automatically organizes entries into Features, Bug Fixes, Performance improvements, Documentation updates, and Breaking Changes.

Do I need the GitHub CLI to extract commits for a changelog?

Yes, you need the GitHub CLI to extract commits and pull requests for a changelog. The skill utilizes GitHub CLI alongside Git commands to process repository history and generate the categorized release notes.

What is the best way to create draft release notes for a new version?

The best way to create draft release notes for a new version is to analyze Git history since the last tag. This skill automates that process by extracting merged pull requests to quickly generate your draft release notes.