changelog-automation

Generate project changelogs from Conventional Commits and Semantic Versioning.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/douglasdennys45/zup-demo-ai --skill changelog-automation-douglasdennys45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/douglasdennys45/zup-demo-ai/tree/main/.claude/skills/changelog-automation
Command: npx skills add https://github.com/douglasdennys45/zup-demo-ai --skill changelog-automation-douglasdennys45

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, commitizen, standard-version, semantic-release, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of manually maintaining changelogs, offering an automated solution that adheres to the Keep a Changelog format and Semantic Versioning standards.

Core Features & Use Cases

  • Automated Changelog: Generates changelogs from commits, PRs, and releases.
  • Conventional Commits: Integrates with Conventional Commits for better commit message standards.
  • Release Note Workflows: Streamlines the process of creating release notes.
  • Semantic Versioning: Manages versioning according to the Semantic Versioning specification.
  • Use Case: When you need to maintain a changelog that reflects all changes across releases, this Skill automates the process, saving time and reducing errors.

Quick Start

Set up your project with the changelog-automation Skill and generate your first changelog by running the script 'generate-changelog.sh'.

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 and semantic versioning?

Automated changelog generation is achieved by running the generate-changelog.sh script, which parses Git commit messages and PR descriptions to produce a structured changelog adhering to the Keep a Changelog format and Semantic Versioning standards.

Does this changelog automation tool integrate with standard-version and semantic-release?

Yes, this changelog automation integrates seamlessly with standard-version and semantic-release, along with commitizen, to manage versioning according to the Semantic Versioning specification and streamline release note workflows.

What is the best way to maintain a changelog that reflects all changes across releases without manual errors?

The best way to maintain an accurate changelog without manual errors is to automate the process by parsing conventional commits and PR descriptions directly from your Git repository, ensuring well-structured release notes every time.

Do I need Git and commitizen to use this automated changelog generation workflow?

Yes, you need a Git repository to provide the commit history and PR descriptions, while commitizen helps enforce the Conventional Commits standard required to parse and generate the structured changelog accurately.

How does parsing PR descriptions improve automated release notes compared to parsing commits alone?

Parsing PR descriptions alongside commit messages enriches automated release notes by capturing broader context and structured changes from Git repositories, resulting in a more comprehensive and well-structured changelog for release management.