changelog-generation

Name: changelog-generation
Availability: InStock
Author: Daniel

Generate changelogs and enforce semantic versioning from conventional commits.

Updated Feb 11, 2026

Search Tags:#git #changelog #versioning #conventional commits #commits #releases

Ready to run

npx skills add https://github.com/daniel-heydari-dev/personal-ai-skills --skill changelog-generation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generation
Source: https://github.com/daniel-heydari-dev/personal-ai-skills/tree/main/templates/skills/changelog-generation
Command: npx skills add https://github.com/daniel-heydari-dev/personal-ai-skills --skill changelog-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing software releases by enforcing conventional commit standards and automating changelog generation, ensuring consistency and clarity in your project's release history.

Core Features & Use Cases

Conventional Commits: Guides users on the correct format for commit messages, including types, scopes, and breaking changes.
Semantic Versioning: Explains the MAJOR.MINOR.PATCH versioning scheme and how commit types map to version bumps.
Changelog Generation: Provides templates and code examples for generating human-readable changelogs based on commit history.
Release Process Automation: Outlines manual and automated (GitHub Actions) steps for releasing new versions.

Quick Start

Use the changelog-generation skill to create a new feature commit message.

Frequently Asked Questions about changelog-generation

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

FAQPage Schema

How does conventional commit format automate changelog generation?▼

Conventional commits automate changelog generation by parsing defined commit types, scopes, and breaking change indicators to categorize release notes and determine semantic versioning bumps. This maps structured commit messages directly into human-readable release histories.

How do I map git commit types to semantic versioning bumps?▼

To map git commits to semantic versioning, use conventional commit types: PATCH for fixes, MINOR for new features, and MAJOR for breaking changes. This ensures the version bump accurately reflects the nature of the codebase modifications.

Can I automate semantic versioning releases using GitHub Actions?▼

Yes, you can automate semantic versioning releases using GitHub Actions. The workflow parses conventional commit history to determine the correct version bump and generates the corresponding changelog entries automatically during the release process.

What is the correct conventional commit message format for a new feature?▼

The correct conventional commit format for a new feature uses the type 'feat' followed by an optional scope and a description, such as 'feat(api): add endpoint'. This ensures the commit is categorized correctly for changelog generation and minor version bumping.

Do I need to manually write release notes if I use conventional commits?▼

No, you do not need to manually write release notes if you use conventional commits. The system provides templates and logic to generate human-readable changelogs automatically based on your structured git commit history.

Why is my semantic versioning not bumping correctly with my git commits?▼

Semantic versioning fails to bump correctly when git commits do not adhere to defined conventional commit standards. Ensure every commit specifies the correct type, scope, and breaking change indicator required for accurate release parsing.