changelog-generator

Parse conventional commits to generate categorized changelogs in markdown, JSON, or plain text.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/FortiumPartners/ensemble-vnext --skill changelog-generator-fortiumpartners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/FortiumPartners/ensemble-vnext/tree/main/packages/skills/changelog-generator
Command: npx skills add https://github.com/FortiumPartners/ensemble-vnext --skill changelog-generator-fortiumpartners

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of changelogs by parsing conventional commits, saving developers time and ensuring consistency in release notes.

Core Features & Use Cases

  • Conventional Commit Parsing: Understands commit types, scopes, subjects, and breaking changes.
  • Automated Categorization: Groups changes into sections like Features, Bug Fixes, and Breaking Changes.
  • Use Case: After merging a feature branch, use this Skill to generate an updated changelog entry for the next release, automatically including the new feature and any related bug fixes.

Quick Start

Use the changelog-generator skill to generate a markdown changelog from the last tag to HEAD.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate changelogs from conventional commits automatically?

Generate changelogs from conventional commits by parsing commit types, scopes, and breaking changes to automatically categorize release notes into sections like Features and Bug Fixes. This automation parses Git history to output structured markdown, JSON, or plain text formats.

What is the best way to create release notes for a multi-repository project?

Creating release notes for a multi-repository project is handled by parsing conventional commits across multiple repository structures to generate a unified changelog. This approach aggregates Git commit histories into a single, categorized release document with semantic version suggestions.

Can I customize the categorization of bug fixes and features in my markdown changelog?

Customizing the categorization of bug fixes and features in a markdown changelog is supported through custom categorization rules. You define how conventional commit types are grouped, allowing the changelog generator to output tailored release notes sections.

How do conventional commits map to semantic version suggestions in release management?

Conventional commits map to semantic version suggestions by analyzing commit types and breaking changes to calculate the next version bump. The changelog generator identifies breaking changes for major versions and features or fixes for minor and patch increments.

Does the changelog generator work without external dependencies or scripts?

The changelog generator works without external dependencies, utilizing internal scripts and references to parse Git commit history. It processes conventional commits natively to produce categorized changelogs in markdown, JSON, or plain text formats.