changelog

Generate and update CHANGELOG.md files following Keep a Changelog standards.

22|1|Updated Jan 10, 2026

Search Tags:#changelog #templates #versioning #semver #docs #release-notes #keepachangelog

Ready to run

npx skills add https://github.com/itechmeat/llm-code --skill changelog-itechmeat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/itechmeat/llm-code/tree/main/skills/changelog
Command: npx skills add https://github.com/itechmeat/llm-code --skill changelog-itechmeat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill standardizes and automates the creation and maintenance of CHANGELOG.md files using the Keep a Changelog format, ensuring consistency across releases.

Core Features & Use Cases

Format structure guidance: Provides the required Unreleased and version sections, with proper headings and versioning guidelines.
Best-practice rules: Enforces ISO dates, link references, and clear categorization of Added, Changed, Fixed, and other change types.
Use Case: A product team generates release notes for a new software version by following the template, then updates it with each change log entry.

Quick Start

Use the changelog skill to generate a new CHANGELOG.md with an Unreleased section and a 1.0.0 entry template.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I maintain a changelog following the Keep a Changelog format?▼

To maintain a Keep a Changelog file, you structure entries under Unreleased and version sections, applying ISO 8601 dates and categorizing changes into Added, Changed, Fixed, and other types for consistent release notes.

What is the Keep a Changelog standard for software release notes?▼

The Keep a Changelog standard is a format for documenting project changes, requiring version headers, ISO 8601 dates, link references, and clear mapping of change types to specific sections within a CHANGELOG.md file.

How do I generate a CHANGELOG.md file with an Unreleased section and version template?▼

You generate a CHANGELOG.md file by creating an Unreleased section alongside a 1.0.0 entry template, using proper headings and versioning guidelines to standardize your project's release documentation.

Does this changelog format support semantic versioning and link references?▼

Yes, the changelog format supports semantic versioning by enforcing version headers and link references, ensuring each release maps clearly to its corresponding semver tag and change categories.

Can I use this changelog template for software projects with varying release cadences?▼

Yes, you can use this changelog template for software projects of varying sizes and release cadences, as it standardizes versioned sections and entry types to accommodate different update frequencies.

Why use ISO 8601 dates and specific change type categories in versioning docs?▼

You use ISO 8601 dates and specific change type categories in versioning docs to enforce best-practice rules, ensuring clear categorization of Added, Changed, and Fixed entries for consistent release tracking.