changelog-generator

Generate changelog entries from Conventional Commits in Markdown or JSON formats.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill changelog-generator-fantasia1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Fantasia1999/claude-skills-zh/tree/main/translations/engineering/changelog-generator
Command: npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill changelog-generator-fantasia1999

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of consistent and auditable release notes by parsing Conventional Commits, eliminating the manual effort and potential for errors in release documentation.

Core Features & Use Cases

  • Automated Changelog Generation: Parses commit messages to generate release notes in Keep a Changelog format.
  • Commit Linting: Enforces Conventional Commits standards to ensure commit message quality.
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically generate a draft of your release notes whenever a new tag is pushed, ensuring all changes are accurately documented.

Quick Start

Use the changelog generator skill to create markdown entries from git tags v1.3.0 to v1.4.0.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I automate changelog generation from conventional commits?

Automating changelog generation from conventional commits involves parsing commit messages to automatically draft release notes in Keep a Changelog format, eliminating manual effort and errors in release documentation.

How does a commit linter enforce commit message standards for release notes?

A commit linter enforces commit message standards by validating submitted messages against Conventional Commits rules, ensuring that automated release notes and semantic version bumping parse the repository history accurately.

Can I integrate automated changelog generation into my CI/CD pipeline?

You can integrate automated changelog generation into your CI/CD pipeline to automatically generate a draft of your release notes whenever a new git tag is pushed, ensuring all changes are accurately documented.

What output formats are supported when generating release notes from git tags?

Generating release notes from git tags supports output formats like Markdown and JSON, allowing you to format parsed Conventional Commits data for different automated release management and documentation needs.

How do I generate a markdown changelog between two git tags?

To generate a markdown changelog between two git tags, configure the generator to parse the commit history from the starting tag to the ending tag, producing structured release notes in Keep a Changelog format.

Does semantic version bumping require strict conventional commit formats?

Semantic version bumping relies on strict conventional commit formats to automatically determine whether to increment major, minor, or patch versions, making commit linting crucial for accurate automated release management.