changelog

Convert conventional commits into Keep a Changelog-compliant release notes.

2|Updated Mar 25, 2026

Search Tags:#automation #changelog #ci-cd #semantic-versioning #release-notes #conventional-commits #keep-a-changelog

Ready to run

npx skills add https://github.com/slabgorb/sidequest --skill changelog-slabgorb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/slabgorb/sidequest/tree/main/.pennyfarthing/skills/pf-changelog
Command: npx skills add https://github.com/slabgorb/sidequest --skill changelog-slabgorb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains consistent, standards-based changelogs and simplifies releasing software by turning git history and conventional commits into ready-to-publish notes.

Core Features & Use Cases

Keeps a CHANGELOG.md in Keep a Changelog format.
Parses conventional commits to populate Added/Changed/Fixed sections.
Auto-generates sections from git history and suggests semantic version bumps.
Prepares release notes and integrates with CI/CD for automated publishing.

Quick Start

Run the changelog skill on your project to generate an up-to-date CHANGELOG.md from git history and conventional commits.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I auto-generate a changelog from conventional commits?▼

Auto-generate a changelog from conventional commits by parsing git history to populate Added, Changed, and Fixed sections, producing a Keep a Changelog-compliant CHANGELOG.md file ready for publication.

What is the Keep a Changelog format for release notes?▼

Keep a Changelog format structures release notes into standardized sections like Added, Changed, and Fixed, ensuring end-user documentation remains consistent and ready for publication. It separates unreleased changes from released semantic versions.

Can I use semantic versioning to suggest release bumps from git history?▼

Yes, semantic versioning decisions are guided by analyzing conventional commits in git history. The skill suggests appropriate version bumps for unreleased and released versions based on commit message types.

How do I prepare release notes for automated CI/CD publishing?▼

Prepare release notes for automated CI/CD publishing by using structured frontmatter-driven metadata to maintain a CHANGELOG.md. This ensures end-user documentation remains consistent and ready for automated release preparation.

Does this changelog automation work without external dependencies?▼

Yes, this changelog automation runs without external dependencies. It converts git history and conventional commits into ready-to-publish notes independently, requiring no additional component setup.

Why should I use conventional commits for changelog maintenance?▼

Conventional commits enable automated changelog maintenance by providing structured commit messages that can be parsed to populate standardized release note sections, simplifying software releases and ensuring documentation consistency.