skills.rest
Jhabbig
JhabbigCOMMUNITY
Explore all skills by this author →
GitHub

changelog-automation

Generate changelogs from commits and pull requests with Keep a Changelog formatting.

Updated Apr 5, 2026
Search Tags:#changelog#versioning#github-actions#semantic-versioning#release-notes#conventional-commits#release-automation
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill changelog-automation-jhabbig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/Jhabbig/Habbig --skill changelog-automation-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual effort of assembling release notes, keeping changelogs consistent and ready to ship whenever code changes are cut into versions.

Core Features & Use Cases

  • Conventional Commits mapping: Organize feat, fix, refactor, and revert entries into predictable changelog sections.
  • Release automation: Support standard-version, semantic-release, git-cliff, commitizen, and GitHub Actions workflows.
  • Use Case: A team preparing a versioned release can convert recent commits and merged pull requests into clean release notes and update the changelog automatically.

Quick Start

Ask the skill to generate a Keep a Changelog workflow for your repository using your preferred release tool and commit style.

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 automatically from conventional commits?▼

Automated changelog generation maps conventional commit types like feat, fix, and refactor into structured release note sections. It uses commit history to assemble Keep a Changelog formatted output automatically, eliminating manual documentation effort during versioned releases.

How does semantic versioning work with GitHub Actions release automation?▼

GitHub Actions release automation uses conventional commit prefixes to trigger semantic versioning bumps, generating tagged releases and formatted changelog updates automatically within your CI workflow.

Can I use Keep a Changelog formatting with semantic-release and commitizen?▼

Yes, semantic-release and commitizen support Keep a Changelog formatting by mapping conventional commit prefixes into standardized release note sections, ensuring consistent changelog structure across Node.js and Python environments.

What is the best way to turn pull requests into release notes automatically?▼

The best way to turn pull requests into release notes is using conventional commit mapping within CI workflows. Tools like standard-version and git-cliff parse merged pull request titles and descriptions to populate structured changelog entries automatically.

Does automated changelog generation support both Node.js and Python release workflows?▼

Yes, automated changelog generation supports Node.js and Python release workflows. It integrates with semantic-release, git-cliff, and GitHub Actions to apply semantic versioning and Conventional Commits mapping across different runtime environments.

Related Skills

Explore More Software Engineering Skills→
wolf5996wolf5996
5

git-hygiene

Standardize Git commit messages, branching, and history rewrites.

Community
Basic
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
monforjemonforje

golang-continuous-integration

Automate Golang CI/CD pipelines with GitHub Actions for testing, linting, and releases.

Community
Advanced
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced