changelog-generator

Generate changelogs from git commits following detected versioning and formatting conventions.

Updated Apr 20, 2020
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill changelog-generator-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill changelog-generator-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing changelogs from git history is tedious and error-prone, especially when projects use different versioning schemes and changelog formats. This Skill automates the process by detecting your project's conventions and generating consistent, well-formatted changelog entries. ## Core Features & Use Cases - Automatic Convention Detection: Detects versioning style (SemVer, two-component, CalVer) from CLAUDE.md, git tags, or existing CHANGELOG.md files. - Format Adaptation: Supports both Keep a Changelog (h2) and pf4j-style (h3) formats, matching your existing file's section order and link style. - Reference-Style Links: Generates clean [#123] issue references with link definitions and GitHub version comparison URLs. - Use Case: Before cutting a release, ask for a changelog since the last tag and receive a grouped entry (Added/Changed/Fixed) mapped from conventional commits, plus a suggested version bump. ## Quick Start Ask the AI to generate a changelog for all commits since the last release tag in this repository.

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 commits?▼

Run the changelog generator after your last release tag. It reads commits via git log, maps conventional commit types (feat, fix, perf) to changelog sections, and outputs a formatted entry with issue links and a suggested version bump.

How to detect which versioning scheme a project uses?▼

The skill checks CLAUDE.md for an explicit versioning section first, then analyzes git tag patterns (v3.15.0 indicates SemVer, 2026.01 indicates CalVer), then falls back to the existing CHANGELOG.md format before asking the user.

Does it support Keep a Changelog and other formats?▼

Yes, it supports both Keep a Changelog (h2 version headings) and pf4j-style (h3 version headings) formats. It detects the existing file's heading level, section order, and link style, then matches them when inserting new entries.

What happens if commits don't follow conventional commits?▼

Non-conventional commits are listed under the Changed section with their original messages. The skill works best with conventional commits but handles legacy history gracefully without failing.

How are breaking changes handled in the changelog?▼

Breaking changes are placed in the Changed section with a bold BREAKING prefix and the issue reference. They also trigger a major version bump suggestion in SemVer and two-component versioning schemes.