changelog-generator

Generate user-facing changelogs from git commit history.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill changelog-generator-plurigrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/plurigrid/asi/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/plurigrid/asi --skill changelog-generator-plurigrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically creates user-facing changelogs from git commits by analyzing history, categorizing changes, and translating technical commits into clear release notes.

Core Features & Use Cases

  • Scan Git history and between versions
  • Categorize changes (features, improvements, fixes, breaking changes, security)
  • Translate technical commits into customer-friendly language
  • Produce well-formatted, publication-ready notes

Quick Start

Generate a changelog for commits since the last release and format it for a public changelog page.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate a changelog from git commit history?

Generate a changelog by scanning your git commit history within a defined time window, categorizing changes into features, improvements, bug fixes, breaking changes, and security updates, then translating technical commit messages into customer-friendly language for publication-ready release notes.

Can I automate changelog creation between software versions?

Yes, automate changelog creation by analyzing git history between version tags, extracting and categorizing commits, filtering out noise like refactoring and test changes, and formatting the output as professional release notes aligned with your brand guidelines.

What's the best way to turn technical commits into user-facing release notes?

Translate technical commits into release notes by categorizing them by change type, filtering irrelevant entries, applying a CHANGELOG_STYLE to match your brand voice, and formatting entries for clarity so customers understand what changed without technical jargon.

Does this work for app store descriptions and public changelog pages?

Yes, use changelog generation for multiple release documentation formats: app store descriptions, public changelog pages, internal release documentation, weekly or monthly update summaries, all using the same categorized and customer-friendly translated content from your git history.

How do I filter out noise like refactoring commits from my changelog?

Automatically filter noise by categorizing commits into meaningful change types—features, improvements, fixes, breaking changes, and security—which excludes refactoring, test-only commits, and internal documentation changes from the final customer-facing changelog.