Changelog Generator Skill

Generate categorized changelogs from conventional commits in markdown, JSON, or plain text.

11|1|Updated Aug 24, 2025
One-click install
npx skills add https://github.com/FortiumPartners/ai-mesh --skill changelog-generator-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Changelog Generator Skill
Source: https://github.com/FortiumPartners/ai-mesh/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/FortiumPartners/ai-mesh --skill changelog-generator-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill converts conventional commits into structured, categorized changelogs, enabling teams to publish accurate release notes and drive clear version decisions.

Core Features & Use Cases

  • Conventional Commit Parsing: extract type, scope, subject, breaking changes from commit messages.
  • Category-based Changelog: automatically group commits into Features, Bug Fixes, Breaking Changes, Performance, and Documentation.
  • Multi-format Output: produce Markdown, JSON, or plain text changelogs for various release artifacts.
  • Use Case: run the generator on a repo to create a ready-to-publish CHANGELOG when preparing a release.

Quick Start

Run the generator against your git history to output a Markdown changelog.

Frequently Asked Questions about Changelog Generator Skill

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

FAQPage Schema
How do I generate release notes from conventional commits?

Generate release notes from conventional commits by parsing git history to extract type, scope, subject, and breaking changes, then automatically grouping them into categorized changelog sections. The skill outputs structured release notes ready for publication.

What's the best way to group git commits into categories for a changelog?

Group git commits into categories for a changelog by mapping conventional commit types to predefined sections such as Features, Bug Fixes, Breaking Changes, Performance, and Documentation. This automated category mapping ensures structured and readable release notes.

Can I output my changelog as JSON or plain text instead of markdown?

You can output your changelog as JSON, plain text, or markdown. This multi-format output capability supports various release artifacts and integration pipelines, allowing you to select the format that best fits your downstream release process.

Does this changelog generator support multi-repo histories?

This changelog generator supports multi-repo histories. It applies to release pipelines across multiple repositories, parsing conventional commits from combined git histories to produce a unified and categorized changelog for your release.

How does conventional commit parsing handle breaking change detection?

Conventional commit parsing handles breaking change detection by extracting breaking change indicators from commit messages. It enforces this detection to ensure breaking changes are explicitly highlighted in the changelog and reflected in semantic versioning suggestions.

Can I get semantic versioning suggestions from my git history?

You can get semantic versioning suggestions from your git history by configuring a current version. The generator analyzes parsed conventional commits and detected breaking changes to recommend the next appropriate semantic version for your release.