changelog

Generate human-readable changelog entries from git history and diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates human-friendly release notes by deriving changelog entries from git history and diffs, transforming structured commit data into readable user-facing changes.

Core Features & Use Cases

  • Identify the commit range for a release and read messages
  • Ignore non-user-visible changes (formatting, internal refactors) and group by impact
  • Output sections (Added, Changed, Fixed, Removed, Security, Infrastructure) in clear language
  • Use when drafting release notes or preparing customer-facing documentation

Quick Start

Generate a changelog for the commits between the latest tag and HEAD

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from git history and diffs?

Generate release notes from git history by identifying a commit range, parsing commit messages, filtering non-user-facing changes, and categorizing entries into readable sections like Added, Changed, and Fixed.

How does changelog generation filter internal refactoring commits?

Changelog generation filters internal refactoring commits by parsing git history to ignore non-user-visible changes such as formatting adjustments, ensuring only impactful modifications appear in the final release notes.

What's the best way to group git commits into release note sections?

Group git commits into release note sections by categorizing parsed commit messages into standard classifications like Added, Changed, Fixed, Removed, Security, and Infrastructure based on their user-facing impact.

Can I use git tags to define a commit range for release notes?

Yes, you can use git tags to define a commit range for release notes. The process reads commit messages between a specified tag and HEAD to prepare customer-facing documentation for a specific release.

Does automated changelog generation work for stakeholder communication?

Automated changelog generation works for stakeholder communication by transforming structured git commit data into clear, human-readable entries that highlight user-facing changes across multiple commits and tags.

When do I need to exclude non-user-visible changes from project documentation?

Exclude non-user-visible changes from project documentation when drafting release notes to ensure customer-facing communication focuses strictly on impactful updates rather than internal formatting or infrastructure refactoring.