Changelog Generator

Generate markdown and JSON changelog entries from Conventional Commits.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/tapanshah/Claude-Skills --skill changelog-generator-tapanshah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Changelog Generator
Source: https://github.com/tapanshah/Claude-Skills/tree/main/engineering/changelog-generator
Command: npx skills add https://github.com/tapanshah/Claude-Skills --skill changelog-generator-tapanshah

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of release notes by parsing Conventional Commits, ensuring consistency and saving significant time in the release process.

Core Features & Use Cases

  • Automated Changelog Generation: Creates release notes in Keep a Changelog format from git commit history.
  • Commit Linting: Enforces Conventional Commits standards to maintain quality and structure.
  • CI Integration: Designed for seamless integration into CI/CD pipelines for automated releases and PR checks.
  • Use Case: Before publishing a new version, run this skill to generate the CHANGELOG.md entry automatically from the commits made since the last release.

Quick Start

Generate a markdown changelog entry for the commits between v1.2.0 and v1.3.0.

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 conventional commits automatically?

You can generate release notes by parsing conventional commits to extract types, scopes, and breaking changes. This process creates structured changelog entries in Keep a Changelog format, outputting either markdown or JSON files from your git history.

What is the best way to automate a changelog in a CI/CD pipeline?

Automating a changelog in a CI/CD pipeline involves integrating commit linting and release note generation scripts directly into your workflow. This automatically parses commit history between tags to produce structured release documentation during deployments.

Can I lint git commit messages against conventional commits rules?

Yes, you can lint git commit messages to enforce conventional commits standards. This validates commit structure, ensuring quality and consistency before automatically generating release notes from the parsed commit history.

Does changelog generation support JSON output or only markdown?

Changelog generation supports both JSON and markdown output formats. This allows you to output structured release documentation in markdown for human-readable changelogs or JSON for programmatic integration.

How do I create a changelog entry for commits between two git tags?

To create a changelog entry for commits between two git tags, you parse the commit history from the starting tag to the ending tag. The generator extracts conventional commit types and scopes to produce the structured release notes.