changelog-generator

Generate structured release notes from git commit history.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/quany/skills --skill changelog-generator-quany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/quany/skills/tree/main/changelog-generator
Command: npx skills add https://github.com/quany/skills --skill changelog-generator-quany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of user-facing release notes from git commit history, reducing manual drafting time and improving accuracy.

Core Features & Use Cases

  • Automated changelog generation: Analyzes commit history to produce structured release notes.
  • Commit categorization: Groups changes into features, improvements, bug fixes, breaking changes, and security.
  • Use Case: Prepare customer-facing release notes for new versions, weekly updates, or app store submissions.

Quick Start

From your project repository, run the changelog generator on the desired commit window to generate a consumer-ready changelog. Example: changelog-generator --since last_release --output CHANGELOG.md

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate user-facing release notes from git commit history?

To generate release notes from git commit history, you can automate the process by analyzing your commits, categorizing changes into features or bug fixes, and outputting structured changelogs that align with your brand voice.

How are commits categorized when creating automated changelogs?

When creating automated changelogs, commits are categorized by grouping changes into distinct groups such as features, improvements, bug fixes, breaking changes, and security updates to produce structured output.

Can I use automated changelog generation for app store submissions and weekly updates?

Yes, automated changelog generation applies to software projects of any size and supports preparing customer-facing release notes for new versions, weekly updates, and app store submissions.

What is the best way to structure release notes for a new software version?

The best way to structure release notes is to analyze a specific commit window since the last release, categorize the changes, and output a readable changelog file like CHANGELOG.md.

Do I need any specific dependencies to run the changelog generator?

No specific dependencies are required to run the changelog generator, as it operates independently within your project repository to analyze commit windows and produce structured documentation.