changelog-generator

Generate a changelog from conventional commits with Added, Changed, Fixed, and Deprecated sections.

1|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/iCesofT/awesome-ai --skill changelog-generator-icesoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/iCesofT/awesome-ai/tree/main/skills/05-deployment-changelog-generator
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill changelog-generator-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a coherent changelog by aggregating and formatting entries from conventional commits, aligning release notes with minimal manual effort.

Core Features & Use Cases

  • Automated Changelog: Builds a structured changelog from standardized commit messages.
  • Release-Ready Output: Produces sections for Added, Changed, Fixed, and Deprecated aligned to semantic conventions.
  • Use Case: Before a release, generate a changelog that documents new features, fixes, and breaking changes for stakeholders.

Quick Start

Generate a comprehensive changelog from the latest set of commits for the project.

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 conventional commits for a Java project?

Generate a changelog from conventional commits by aggregating standardized commit messages into a coherent, release-ready document. It automatically groups Java project history into Added, Changed, Fixed, and Deprecated sections.

What is the best way to automate release notes preparation before a deployment?

Automate release notes preparation by summarizing commit history into a deterministic changelog aligned with semantic conventions. This builds release-ready documentation of new features and fixes for stakeholders with minimal manual effort.

Does this changelog generator work with Git commits that don't follow conventional formats?

This changelog generator enforces conventional-commit-based grouping, meaning it expects Git commits formatted with standard prefixes like Added, Changed, Fixed, and Deprecated to produce a coherent release-ready document.

Can I use this for auditing changes across pre-release workflows in Java projects?

Yes, you can use this for auditing changes across pre-release workflows in Java projects. It summarizes commit history to document fixes and breaking changes, producing a deterministic, release-ready audit trail.

How do release notes grouping sections like Added and Fixed get populated automatically?

Release notes grouping sections like Added and Fixed get populated automatically by applying conventional-commit-based grouping to your commit history. This enforces semantic conventions to output a structured, deterministic changelog.