changelog-automation

Generate changelogs from commits, pull requests, and releases.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill changelog-automation-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/changelog-automation
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill changelog-automation-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of assembling changelogs, release notes, and version bumps from commits, pull requests, and releases, making release management consistent and repeatable.

Core Features & Use Cases

  • Keep a Changelog Structure: Produces release history in a standard format that is easy to read and maintain.
  • Conventional Commits Mapping: Translates feat, fix, refactor, and other commit types into the right changelog sections.
  • Release Automation Workflows: Supports standard-version, semantic-release, git-cliff, commitizen, and GitHub Actions for automated publishing.
  • Use Case: A team preparing a new release can generate notes, bump versions, and publish a polished changelog without editing the file by hand.

Quick Start

Ask for an automated changelog workflow that turns your commit history into a Keep a Changelog release note process with semantic versioning support.

Frequently Asked Questions about changelog-automation

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

FAQPage Schema
How do I automate changelog generation from conventional commits?

Automating changelog generation from conventional commits involves mapping commit types like feat, fix, and refactor into structured release notes. This process translates your commit history into a Keep a Changelog format without manual editing.

What is the best way to generate release notes with semantic versioning?

Generating release notes with semantic versioning is best achieved by applying automated release workflows. Tools like standard-version or semantic-release analyze commit history to bump versions and publish formatted changelogs automatically.

Does semantic-release work with Keep a Changelog formatting?

Yes, semantic-release integrates with Keep a Changelog formatting by mapping conventional commit types to standard changelog sections. This combination allows automated publishing of consistent, readable release notes.

Can I use GitHub Actions to publish changelogs to GitLab releases?

GitHub Actions can automate changelog generation and support publishing release notes for both GitHub and GitLab releases. This workflow uses tools like git-cliff or commitizen to turn pull requests into polished release notes.

How do conventional commits map to Keep a Changelog sections?

Conventional commits map to Keep a Changelog sections by translating commit prefixes like feat into Added and fix into Fixed. This mapping ensures release notes reflect semantic versioning changes accurately.

Why should teams enforce commit conventions for release notes automation?

Enforcing commit conventions for release notes automation eliminates the manual toil of assembling changelogs by hand. Consistent conventional commits allow automated semantic versioning and accurate release history generation.