changelog-automation

Generate Keep a Changelog–aligned CHANGELOG.md files from commits, PRs, and releases.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/haxlys/skills --skill changelog-automation-haxlys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/haxlys/skills/tree/main/vendored/wshobson-agents/plugins/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/haxlys/skills --skill changelog-automation-haxlys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates keeping project changelogs up-to-date by aggregating commits, PRs, and releases into a standardized Keep a Changelog format.

Core Features & Use Cases

  • Generate release notes from Conventional Commits and semantic versioning metadata.
  • Create and update CHANGELOG.md automatically during release workflows for GitHub-, GitLab-, and other VCS-based projects.
  • Provide templates and guidance for releases, including added, changed, fixed sections, and contributor notes.
  • Enable consistent, auditable release documentation to improve transparency and collaboration.

Quick Start

Run the changelog-automation tool on your repository to produce a Keep a Changelog–aligned CHANGELOG.md for the latest release.

Frequently Asked Questions about changelog-automation

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

FAQPage Schema
How do I automatically generate a changelog from conventional commits?

Generate a changelog from conventional commits by aggregating repository commits, PRs, and releases into a standardized Keep a Changelog format automatically during your release workflow. This process uses semantic versioning metadata to categorize changes.

Can I automatically update CHANGELOG.md for GitHub and GitLab releases?

Yes, you can automatically create and update CHANGELOG.md for GitHub, GitLab, and other VCS-based projects. The automation runs during release workflows to ensure your project documentation stays current across multiple repositories.

What is the Keep a Changelog format and how does it organize release notes?

The Keep a Changelog format organizes release notes into standardized sections like added, changed, fixed, and contributor notes. It provides consistent, auditable release documentation by applying semantic versioning and conventional commit standards to your project history.

Does automated changelog generation work with semantic versioning metadata?

Yes, automated changelog generation works directly with semantic versioning metadata and conventional commits. It uses this information to categorize your repository history accurately into the appropriate Keep a Changelog sections for each release.

How do I standardize commit conventions across multiple repositories for release notes?

Standardize commit conventions across multiple repositories by applying conventional commits and semantic versioning rules to generate consistent release notes. This provides automated template-based changelog generation to ensure uniform documentation across all your VCS projects.