Changelog Generator

Name: Changelog Generator
Availability: InStock
Author: aman

Generate changelog entries from Conventional Commits in markdown or JSON.

Updated Feb 27, 2026

Search Tags:#automation #git #changelog #ci/cd #conventional commits #release notes

Ready to run

npx skills add https://github.com/amanhsn/flyerbuild --skill changelog-generator-amanhsn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Changelog Generator
Source: https://github.com/amanhsn/flyerbuild/tree/main/.cursor/skills/changelog-generator
Command: npx skills add https://github.com/amanhsn/flyerbuild --skill changelog-generator-amanhsn

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 from git history or provided commit data.
Commit Linting: Enforces Conventional Commit standards to maintain message quality.
Use Case: Before publishing a new version, use this skill to automatically generate a draft of your CHANGELOG.md file based on the commits made since the last release.

Quick Start

Generate a markdown changelog entry for 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 automate changelog generation from conventional commits?▼

You can automate changelog generation by parsing git history or provided commit data into structured markdown or JSON release notes. This process validates commit message formats against defined rules to ensure consistency for automated release workflows.

Can I automatically update an existing CHANGELOG.md file with new release notes?▼

Yes, you can perform optional in-place file updates to append new release notes directly to an existing changelog. This allows seamless integration into your automated release process without manual file editing.

How do I enforce conventional commit standards in a CI/CD pipeline?▼

You can enforce conventional commit standards by integrating commit linting into your CI/CD pipelines. The system validates commit message formats against defined rules, ensuring adherence to standards before automated release note generation proceeds.

What is the best way to generate release notes between two git tags?▼

The best way to generate release notes between tags is to parse the conventional commits within that specific git history range. The tool outputs structured markdown or JSON entries, providing a clean draft for your release workflow.

Does this changelog generator support JSON output for automated workflows?▼

Yes, the changelog generator supports both markdown and JSON output formats. JSON output allows downstream CI/CD processes to programmatically consume and manipulate the generated release notes.

Why should I validate commit messages before generating release notes?▼

Validating commit messages ensures adherence to conventional commit standards, which is necessary for accurate automated release note generation. Without proper validation, inconsistent commit data will produce fragmented or incorrect changelog entries.