mm-changelog

Generate a Keep a Changelog changelog from conventional Git commits.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mm-changelog
Source: https://github.com/mikkeymoo/claude-solo/tree/main/mm-skills/mm-changelog
Command: npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of a changelog from conventional commits, saving time and reducing the potential for errors in manual changelog creation.

Core Features & Use Cases

  • Conventional Commit Parsing: Automatically parses conventional commits from the repository history.
  • Changelog Generation: Generates a markdown-formatted changelog based on the parsed commits.
  • Modes: Offers different modes such as preview, write, and since to cater to various use cases.

Quick Start

Run the /mm-changelog --preview command to generate a preview of the changelog.

Frequently Asked Questions about mm-changelog

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

FAQPage Schema
How do I automate changelog generation from Git conventional commits?

Automating changelog generation involves parsing conventional commit messages from a Git repository and formatting them into Markdown. This process eliminates manual entry errors and saves time.

Can I preview changes before writing them to a Keep a Changelog formatted file?

Yes, you can preview changes before writing them by using a preview mode. This allows you to review the parsed conventional commits and the generated Markdown output before committing the file updates.

Does Python need to be installed to parse commit history and generate Markdown?

Yes, Python is required to execute the commands that parse Git commit history and generate the changelog output. Git is also necessary to access the repository and read the conventional commit messages.

How do I filter commits by tag when creating a Markdown changelog?

You can filter commits by tag to isolate specific release boundaries when creating a Markdown changelog. This ensures only the relevant conventional commits between tags are included in the generated output.

What is the best way to maintain a Keep a Changelog format using conventional commits?

The best way to maintain a Keep a Changelog format is to automatically parse conventional commits and append them to the changelog. This ensures consistent formatting and accurate documentation of repository changes.