changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

4|1|Updated Mar 15, 2026

Search Tags:#automation #git #changelog #semantic-versioning #release-notes #conventional-commits #keep-a-changelog

Ready to run

npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill changelog-gen-faysilalshareef

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/docs/changelog-gen
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill changelog-gen-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate consistent, human-readable changelogs and release notes from raw git history so teams no longer maintain manual or ad-hoc changelog files and miss important changes during releases.

Core Features & Use Cases

Conventional Commit Parsing: Extract and categorize commits using conventional commit types into standard changelog sections.
Keep a Changelog Formatting: Produce CHANGELOG.md content that follows the Keep a Changelog structure with Added, Changed, Deprecated, Removed, Fixed, and Security sections.
Semantic Versioning Guidance: Suggest version bumps (major/minor/patch) based on commit types and support per-service microservice changelogs as well as combined release notes for monorepos.
Release Notes Output: Generate GitHub-friendly release notes summarizing highlights, bug fixes, and infrastructure changes.

Quick Start

Run the changelog-gen skill to build an Unreleased changelog section from commits since the last tag.

Frequently Asked Questions about changelog-gen

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

FAQPage Schema

How do I generate a changelog from git commit history?▼

To generate a changelog from git history, the Skill parses conventional commit messages and groups them into Keep a Changelog sections like Added, Changed, and Fixed. This produces a structured CHANGELOG.md directly from your repository history.

Does this work with repositories that don't use conventional commits?▼

No, generating structured changelogs requires repositories that follow conventional commits and semantic versioning. The Skill relies on conventional commit types like feat or fix to categorize entries accurately into Keep a Changelog sections.

How does semantic versioning guidance work with conventional commits?▼

Semantic versioning guidance analyzes your conventional commit types to suggest appropriate version bumps. Breaking changes suggest a major bump, new features suggest a minor bump, and fixes suggest a patch bump for your release.

Can I generate release notes for microservice or monorepo workflows?▼

Yes, you can generate changelogs for both single-repo and microservice workflows. The Skill supports per-service microservice changelogs as well as combined release notes for monorepos to summarize highlights across multiple services.

What is the best way to format a CHANGELOG.md file?▼

The best way to format a CHANGELOG.md is using the Keep a Changelog structure, which organizes changes into Added, Changed, Deprecated, Removed, Fixed, and Security sections. This provides consistent, human-readable release notes.