changelog-automation

Generate changelogs from Conventional Commits and manage semantic versioning.

9|3|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Kahtaf/OpenCandle --skill changelog-automation-kahtaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/Kahtaf/OpenCandle/tree/main/.agents/skills/changelog-automation
Command: npx skills add https://github.com/Kahtaf/OpenCandle --skill changelog-automation-kahtaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and managing changelogs for software projects, ensuring that release notes are up-to-date and consistent with the project's versioning and commit conventions.

Core Features & Use Cases

  • Automated Changelog Generation: Dynamically generate changelogs from commits and releases, adhering to the Keep a Changelog format.
  • Release Note Automation: Generate release notes from pull requests and commits following Conventional Commits standards.
  • Semantic Versioning: Helps manage semantic versioning by automatically updating version numbers based on commit types.
  • Use Case: Utilize this Skill in your project to automatically update your CHANGELOG.md and package.json files based on new commits, simplifying the release process.

Quick Start

Use the changelog-automation skill to generate the changelog for your 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 generate a changelog from conventional commits automatically?

To generate a changelog from conventional commits, this Skill parses your commit history and dynamically compiles release notes adhering to the Keep a Changelog format. It automatically categorizes changes based on commit types to maintain an up-to-date changelog file.

How does semantic versioning automation work with commit conventions?

Semantic versioning automation works by analyzing commit messages following Conventional Commits standards to determine the version bump. It automatically updates version numbers in your package.json based on whether commits introduce features, fixes, or breaking changes.

Do I need Conventional Commits standards to automate release notes?

Yes, you need Conventional Commits standards to automate release notes with this Skill. It requires your project to follow these commit conventions to accurately parse commits and pull requests for dynamic release note generation.

What is the best way to maintain a Keep a Changelog format for software releases?

The best way to maintain a Keep a Changelog format is to automate changelog generation directly from your commit history. This Skill dynamically builds and updates your CHANGELOG.md file, ensuring release notes remain consistent with semantic versioning.

Can I update package.json version numbers based on new commits?

Yes, you can update package.json version numbers based on new commits. The Skill manages semantic versioning by reading your Conventional Commits history and automatically applying the correct version bump to your project files.