skills.rest
utkudarilmaz
utkudarilmazCOMMUNITY
Explore all skills by this author →
Website𝕏@utkudarilmazGitHub

changelog

Generate CHANGELOG.md and release notes from git history.

3|Updated Jan 22, 2026
Search Tags:#automation#changelog#versioning#documentation#release-management#release-notes#git-history
One-click install
npx skills add https://github.com/utkudarilmaz/claude-code-setup --skill changelog-utkudarilmaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/utkudarilmaz/claude-code-setup/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/utkudarilmaz/claude-code-setup --skill changelog-utkudarilmaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and maintenance of CHANGELOG.md and release notes from git history, reducing manual toil and ensuring consistent documentation across releases.

Core Features & Use Cases

  • Automated changelog generation: Create and append release notes from commits using a standard format.
  • Release note dispatching: Route to either changelog-generator or release-notes agents based on mode (default, release, or versioned).
  • Versioned history & unreleased sections: Maintain an [Unreleased] section and per-version blocks for clear release tracking.
  • Use Case: Before tagging a new version, auto-generate documentation for stakeholders and users.

Quick Start

Ask the AI to generate a changelog for the latest release using the /changelog command

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate changelog generation from git history?▼

Automating changelog generation from git history involves parsing commit messages to append structured release notes automatically. This skill uses commit data to populate an 'Unreleased' section and per-version blocks, reducing manual documentation toil before tagging a release.

What is the Keep a Changelog format and do I need it for release notes?▼

The Keep a Changelog format is a standard for maintaining human-readable release notes organized by version and change type. This skill requires updates to follow the Keep a Changelog format to ensure consistent documentation across releases and clear release tracking.

How do I generate unreleased sections and per-version notes before tagging a release?▼

Generating unreleased sections and per-version notes is handled by routing to a changelog-generator agent. It maintains an 'Unreleased' block for pending changes and organizes historical entries into distinct per-version sections for clear release tracking.

Can I use this changelog automation for public release announcements?▼

Yes, this changelog automation supports public release announcements by dispatching to a release-notes agent. When run in release or versioned mode, it generates formatted documentation suitable for communicating updates to stakeholders and users.

Does this changelog generator require any external dependencies?▼

No, this changelog generator operates without external dependencies. It functions by analyzing existing git history and formatting updates according to the Keep a Changelog standard, requiring only a standard software project repository.

Related Skills

Explore More Software Engineering Skills→
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
erraggyerraggy
5

publish-release

Validate a version argument and publish a GitHub release from the main branch.

Community
Intermediate
robpitcherrobpitcher

release-process

Automates end-to-end release workflows with semantic versioning validation, npm/GitHub publishing, and rollback support.

Community
Advanced
Andreicr1Andreicr1

api-documentation

Generate HTML, Markdown, and PDF API documentation from OpenAPI specs or code comments.

Community
Advanced