skills.rest
mguinada
mguinadaCOMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate Keep a Changelog–compliant CHANGELOG.md from git history with Semantic Versioning.

Updated Feb 5, 2026
Search Tags:#automation#git#changelog#documentation#semver#release-notes
One-click install
npx skills add https://github.com/mguinada/ai-coding-toolkit --skill changelog-mguinada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/mguinada/ai-coding-toolkit/tree/main/skills/changelog
Command: npx skills add https://github.com/mguinada/ai-coding-toolkit --skill changelog-mguinada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog maintenance is error-prone and time-consuming; this skill automates generating and keeping a Keep a Changelog–compliant CHANGELOG.md up to date from git history and release activity.

Core Features & Use Cases

  • Automatically classify commits into sections such as Added, Changed, Fixed, Deprecated, Removed, and Security.
  • Generate RELEASES.md and, when needed, migration guides for breaking changes.
  • Integrate with release workflows and PR merges to produce user-friendly release notes.

Quick Start

After merging a PR or preparing a new release, run the changelog workflow to generate the latest changelog entries from git history.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate a CHANGELOG.md from git history?▼

You can automatically generate a CHANGELOG.md from git history by aggregating commits, categorizing them into sections like Added or Fixed, and applying Semantic Versioning to structure release notes.

What is the best way to keep a changelog compliant with Keep a Changelog conventions?▼

To keep a changelog compliant, aggregate git history and categorize commits into standard sections like Added, Changed, Fixed, and Removed, while applying SemVer rules to determine version sections.

How do I generate migration guides for breaking changes automatically?▼

Migration guides for breaking changes are generated automatically when major version changes are detected during the git history aggregation process, outputting dedicated documentation alongside your standard changelog.

Can I use git commits to categorize release notes into semantic versioning sections?▼

Yes, you can use git commits to categorize release notes by parsing commit history, classifying entries into standard categories, and organizing them under correct Semantic Versioning release sections.

Does this changelog automation tool require any specific dependencies or environments?▼

This changelog automation requires access to your git history and adherence to Keep a Changelog and Semantic Versioning conventions, but operates without needing external dependencies or component installations.

When should I run the changelog generation workflow during my development cycle?▼

You should run the changelog generation workflow during pre-release preparations or immediately after merging a PR to produce up-to-date, user-friendly release notes from recent git activity.

Related Skills

Explore More Software Engineering Skills→
Prorise-coolProrise-cool
24

changelog-generator

Generate user-facing changelogs from Git commit history.

Community
Intermediate
jonaseck2jonaseck2
2

oss-release

Enforce CHANGELOG.md release-note structure with a 10-block rolling window.

Community
Intermediate
awslabsawslabs
22

ship-it

Enforce conventional commits and PR-based git workflows for controlled releases.

Official
Advanced
vekzz-devvekzz-dev
3

changelog-maintenance

Standardize release documentation with semantic versioning and Keep a Changelog.

Community
Intermediate