changelog-automation

Automate changelog generation and release management with Conventional Commits.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/figuedmundo/mamirri-app --skill changelog-automation-figuedmundo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/figuedmundo/mamirri-app/tree/main/.agents/skills/changelog-automation
Command: npx skills add https://github.com/figuedmundo/mamirri-app --skill changelog-automation-figuedmundo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of changelogs and release notes, ensuring consistency and saving significant developer time.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelogs based on commit messages following Conventional Commits.
  • Release Management: Integrates with tools like semantic-release and standard-version for automated version bumping and tagging.
  • Use Case: Streamline your release process by automatically generating release notes for each new version based on the commits merged since the last release.

Quick Start

Use the changelog-automation skill to generate release notes for the next patch release.

Frequently Asked Questions about changelog-automation

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

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

Automate changelog generation by parsing conventional commit messages to compile structured release notes, ensuring consistent documentation of changes across new versions without manual entry.

What is the best way to automate semantic versioning and release notes in GitHub Actions?

Automate semantic versioning and release notes by integrating semantic-release or standard-version within your GitHub Actions workflows to automatically bump version numbers and tag releases based on commit history.

Does semantic-release work with conventional commits to manage version bumping?

Yes, semantic-release parses conventional commits to determine the type of changes, automatically triggering appropriate semantic version bumps and generating formatted release notes for each tagged release.

Can I use standard-version or git-cliff to streamline my release process?

Yes, standard-version and git-cliff parse conventional commit histories to automatically generate changelogs, bump semantic version numbers, and create tagged releases, streamlining your project's release process.

Why do I need commitizen for automated release management?

Commitizen enforces the conventional commits format during local development, ensuring that commit messages contain the structured metadata required by automated changelog tools to accurately categorize release notes and trigger version bumps.