changelog-gen

Generates categorized Markdown changelog entries from git history between two refs.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/lxgicstudios/ai-changelog --skill changelog-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/lxgicstudios/ai-changelog/tree/main
Command: npx skills add https://github.com/lxgicstudios/ai-changelog --skill changelog-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog maintenance is tedious and error-prone; this Skill automates turning raw commit history into concise, categorized release notes.

Core Features & Use Cases

  • Reads git history between two refs and generates a clean, formatted changelog.
  • Groups changes into Added, Changed, Fixed, Removed for easy scanning.
  • Outputs Markdown ready for inclusion in a CHANGELOG.md or release notes.

Quick Start

Run a single command to generate a changelog from two git refs and view or save the result.

Frequently Asked Questions about changelog-gen

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

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

Automatically generate a changelog by running the CLI tool to read git logs between two refs, categorize commits, and output Markdown release notes. It groups changes into Added, Changed, Fixed, and Removed sections for immediate scanning.

Do I need an OpenAI API key to generate release notes from git logs?

You need an OpenAI API key to generate release notes, as the tool requires the OPENAI_API_KEY environment variable to assist with categorizing and formatting raw commit history into clean changelog entries.

Can I generate Markdown release notes for specific git commit ranges?

Generate Markdown release notes for specific commit ranges by providing two git refs to the CLI command. The workflow isolates the history between those points and formats the output for a CHANGELOG.md file.

What is the best way to format raw git commits into categorized release notes?

The best way to format raw git commits is using an AI-assisted generator that reads history between two refs and automatically categorizes entries into standard Markdown sections like Added, Changed, Fixed, and Removed.

Are there limitations to using AI for changelog generation from git history?

A limitation of using AI for changelog generation is the dependency on the OPENAI_API_KEY environment variable, and the tool specifically requires defining two git refs to isolate the commit range for accurate Markdown output.