changelog

Parse Git history into a structured Markdown changelog with categorized sections.

14|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wpgaurav/WordPress-skills --skill changelog-wpgaurav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/wpgaurav/WordPress-skills/tree/main/skills/tools/changelog
Command: npx skills add https://github.com/wpgaurav/WordPress-skills --skill changelog-wpgaurav

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and maintenance of release notes by deriving them from Git history.

Core Features & Use Cases

  • Parse commits since the last version tag and categorize changes into Added, Changed, Fixed, Removed following Keep a Changelog conventions.
  • Generate or update CHANGELOG.md, including version numbers and publication dates.
  • Link relevant commits or PRs to provide traceability in the changelog.

Quick Start

Generate the latest CHANGELOG.md from your repository's commit history.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from git history automatically?

To generate a changelog from git history, the Skill parses commit logs since the last version tag and categorizes them into Added, Changed, Fixed, and Removed sections in Markdown format.

What is the Keep a Changelog format for release notes?

The Keep a Changelog format structures release notes by categorizing git commits into sections like Added, Changed, Fixed, and Removed, including version numbers and publication dates in a Markdown file.

Does this changelog generator work with conventional commits?

Yes, the changelog generator works with conventional commits by parsing git logs to map commit messages into Keep a Changelog categories like Added, Changed, Fixed, and Removed.

How do I update an existing CHANGELOG.md with new release notes?

To update an existing CHANGELOG.md, the Skill parses recent git commits since the last version tag and generates or appends structured Markdown sections with version numbers and publication dates.

Can I link commits or PRs in my generated Markdown release notes?

Yes, you can link commits or PRs in generated Markdown release notes to provide traceability, connecting the categorized Added, Changed, and Fixed sections directly to their git history sources.