changelog-generator

Generate release notes from git commits with categorized and polished changelog output.

5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill changelog-generator-guicedee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.curated/changelog-generator
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill changelog-generator-guicedee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing release notes from developer commits is tedious and error-prone. This skill automates the generation of clear, customer-facing changelogs directly from git history.

Core Features & Use Cases

  • Automated extraction of commit messages within a date range or between versions.
  • Categorization into features, improvements, fixes, breaking changes, and security updates.
  • Natural-language polishing to translate technical commits into consumer-friendly notes.
  • Professionally formatted output suitable for public release pages, newsletters, and app stores.
  • Use Case: Generate a product release note for version 3.1.0 based on commits since v3.0.0.

Quick Start

Generate a changelog for the latest release by scanning commits since the last tag or a specified date range.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate release notes from git commits automatically?

To generate release notes from git commits automatically, apply this skill to your software project to scan commit history within a date range or between version tags. It outputs formatted, customer-facing release notes summarizing features, fixes, and improvements.

Can I translate technical git commit messages into customer-friendly changelogs?

Yes, you can translate technical git commit messages into customer-friendly changelogs. The skill applies natural-language polishing to convert developer commits into consumer-friendly notes suitable for public release pages and newsletters.

How does automated commit scanning categorize features and fixes for a changelog?

Automated commit scanning categorizes features and fixes by grouping extracted commit messages into distinct categories. It organizes changes into features, improvements, fixes, breaking changes, and security updates for a structured changelog.

What is the best way to summarize weekly software changes for a product release note?

The best way to summarize weekly software changes for a product release note is using automated commit scanning across a specified date range. This groups versioned changes and formats them into a professional changelog adhering to standard practices.

Does this changelog generator work with specific version tags like v3.1.0?

Yes, this changelog generator works with specific version tags. You can generate a product release note by scanning and extracting commit messages between two version tags, such as v3.0.0 and v3.1.0, to identify included changes.

Do I need a specific environment to produce formatted output for app stores and newsletters?

You need a software project with available git commit history to produce formatted output for app stores and newsletters. The skill processes this commit history to generate professionally formatted release notes without requiring additional dependencies.