changelog-generator

Generate CHANGELOG.md from Git commit history using Conventional Commits.

420|63|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/peterfei/ai-agent-team --skill changelog-generator-peterfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/peterfei/ai-agent-team/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/peterfei/ai-agent-team --skill changelog-generator-peterfei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chalk, commander, conventional-changelog-core, conventional-changelog-writer, git-raw-commits, git-semver-tags, handlebars, lodash, semver.

What problem does it solve?

Manually maintaining a CHANGELOG.md is often neglected, inconsistent, and time-consuming for development teams. This skill automates the creation of structured and readable changelogs directly from Git commit history, following Conventional Commits specifications.

Core Features & Use Cases

  • Git History Analysis: Automatically parses Git commit messages and categorizes changes (features, fixes, breaking changes).
  • Conventional Commits Support: Adheres to industry-standard commit message guidelines for consistent changelog entries.
  • Customizable Output: Supports various output formats (e.g., Markdown, HTML) and allows for custom templates to match project branding.
  • Use Case: A software team releases a new version of their product. Instead of manually sifting through Git logs, they use this skill to instantly generate a comprehensive CHANGELOG.md file, detailing all new features, bug fixes, and breaking changes since the last release.

Quick Start

Generate a changelog for the current project since the last tag.

Frequently Asked Questions about changelog-generator

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

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

Automated changelog generation parses your Git commits following Conventional Commits format and produces a structured CHANGELOG.md file. This skill analyzes commit messages to categorize features, fixes, and breaking changes, then outputs them as organized release notes without manual effort.

Can I generate changelogs that follow Conventional Commits standards?

Yes, this skill implements full Conventional Commits support, parsing commit message prefixes like `feat:`, `fix:`, and `BREAKING CHANGE:` to automatically classify and structure changelog entries by change type and severity.

What output formats does changelog generation support?

Changelog generation supports Markdown and HTML output formats with customizable Handlebars templates, allowing you to match your project's branding and documentation style while maintaining consistent structure across releases.

How do I update a changelog incrementally for each new release?

The skill generates incremental updates by analyzing commits since the last Git tag, creating new versioned sections while preserving existing changelog entries, and supports semantic versioning to track release progression.

Does changelog generation integrate with GitHub and GitLab?

Yes, the skill generates release notes compatible with GitHub and GitLab platforms, enabling you to automatically populate release sections with formatted changelog data from your Git history.

What Git commit message structure do I need for effective changelog generation?

Conventional Commits format is required—use structured prefixes like `feat:`, `fix:`, `docs:`, and `BREAKING CHANGE:` in commit messages so the skill can accurately parse and categorize changes into your changelog.