changelog-generator

Generate and update CHANGELOG.md files from git history.

114|12|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/espennilsen/pi --skill changelog-generator-espennilsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/espennilsen/pi/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/espennilsen/pi --skill changelog-generator-espennilsen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and updating of CHANGELOG.md files, ensuring your project's release notes are consistently formatted and informative.

Core Features & Use Cases

  • Automated Changelog Generation: Parses git history to create comprehensive changelogs.
  • Conventional Commits Support: Understands and applies various commit conventions.
  • Use Case: After merging a new release's features and fixes, use this Skill to update your CHANGELOG.md with clear, human-readable entries, linking to relevant PRs and issues.

Quick Start

Use the changelog-generator skill to update the CHANGELOG.md file for the current project.

Frequently Asked Questions about changelog-generator

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

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

To generate a changelog from git history, you can use a tool that parses commit messages and tags to categorize changes into features, bug fixes, and breaking changes. This automates documenting software releases into a CHANGELOG.md file.

Does the changelog generator work with Conventional Commits?

The changelog generator works with Conventional Commits by parsing standard commit messages to accurately categorize new features, bug fixes, and breaking changes into a structured format for release notes.

How do I update an existing CHANGELOG.md file for a new release?

To update an existing CHANGELOG.md file for a new release, the generator analyzes recent git history since the last tag and appends new categorized entries. This ensures your release notes remain consistently formatted without manual editing.

Do I need git command-line tools to generate release notes?

You need git command-line tools installed to generate release notes, because the process requires analyzing commit messages and tags directly from your repository history to categorize changes accurately.

What is the best way to format release notes for software projects?

The best way to format release notes is using the Keep a Changelog format, which structures entries by version and change type. Automating this with git history analysis ensures consistent, human-readable documentation.

Can I link to relevant PRs and issues in my generated changelog?

Yes, the generated changelog can include links to relevant PRs and issues. The tool analyzes commit history and tags to produce clear, human-readable entries that reference associated pull requests and issues for each release.