changelog-generator

Generate a Keep a Changelog compliant CHANGELOG.md from git history using Conventional Commits.

28|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/girijashankarj/cursor-handbook --skill changelog-generator-girijashankarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/girijashankarj/cursor-handbook/tree/main/.cursor/skills/devops/changelog-generator
Command: npx skills add https://github.com/girijashankarj/cursor-handbook --skill changelog-generator-girijashankarj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate a polished CHANGELOG from git history using Conventional Commits to streamline release notes.

Core Features & Use Cases

  • Automated, Keep a Changelog–compliant CHANGELOG generation from commit history.
  • Groups changes into sections like Added, Fixed, Changed, Deprecated, Removed, Security, and Documentation.
  • Supports version range detection, breaking-change detection, and optional comparison links for releases.

Quick Start

Run the bundled script to generate or update CHANGELOG.md from the repository's commit history.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate a changelog from git history using Conventional Commits?

Generate a changelog from git history by parsing commit messages that follow Conventional Commits standards. The tool categorizes commits into sections like Added, Fixed, and Changed, outputting a Keep a Changelog compliant CHANGELOG.md file with version headers and optional diff links.

Does this changelog generator support Keep a Changelog formatting standards?

Yes, this changelog generator supports Keep a Changelog formatting standards. It outputs a structured CHANGELOG.md file organized into sections like Added, Fixed, Changed, Deprecated, Removed, Security, and Documentation with proper version headers.

Can I automatically generate release notes from tag-based releases?

Automatically generate release notes from tag-based releases by detecting version ranges in git history. The tool organizes commits between tags into structured sections and includes optional comparison links for each release.

How are breaking changes detected when creating a changelog?

Breaking changes are detected by parsing commit history for Conventional Commits syntax. When detected, these changes are categorized appropriately within the generated CHANGELOG.md to ensure they are highlighted in the release notes.

Do I need any external dependencies to run this changelog generator?

No external dependencies are required to run this changelog generator. The tool operates using bundled scripts to parse your repository's commit history and generate the CHANGELOG.md file directly.

What is the best way to group commits into Added, Fixed, and Changed sections?

The best way to group commits into Added, Fixed, and Changed sections is by enforcing Conventional Commits formatting in your git history. The generator parses these commit types to automatically categorize changes into a Keep a Changelog compliant structure.