changelog

Generate a HISTORY.md changelog entry from git changes.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Zelenov/frename --skill changelog-zelenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Zelenov/frename/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/Zelenov/frename --skill changelog-zelenov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a HISTORY.md changelog entry based on recent git changes, reducing manual release-note work and ensuring consistent documentation.

Core Features & Use Cases

  • Read git changes (uncommitted, last commit, or between commits) and convert them into a structured changelog.
  • Read HISTORY.md, increment the minor version, reset patch, and prepend the new entry to HISTORY.md.
  • Categorize changes into Added, Changed, Removed, and Fixed for clear release notes.

Quick Start

Create a new HISTORY.md entry from recent git changes and prepend it to HISTORY.md.

Frequently Asked Questions about changelog

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

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

Auto-generating a changelog from git history involves parsing uncommitted changes or specific commits to produce structured release notes categorized into Added, Changed, Removed, and Fixed sections for your HISTORY.md file.

Can I create release notes from uncommitted git changes?

Creating release notes from uncommitted git changes is possible by parsing the current working tree diff, categorizing the modifications, and prepending the formatted entry directly to your HISTORY.md file.

How does version incrementing work when generating a HISTORY.md file?

When generating a HISTORY.md file, the tool reads the existing file, automatically increments the minor version number, resets the patch number to zero, and prepends the new changelog entry with the updated version header.

What is the best way to format git commit messages into structured release notes?

The best way to format git commit messages into structured release notes is to categorize the parsed git diffs into distinct sections like Added, Changed, Removed, and Fixed for clear and consistent documentation.

Do I need to manually categorize git diffs for my changelog entries?

No, you do not need to manually categorize git diffs for your changelog entries as the automation process parses the git history and automatically sorts the changes into standard categories like Added, Changed, Removed, and Fixed.

When should I use an automated changelog generator for versioning?

You should use an automated changelog generator for versioning when you are releasing new features, updating project versions, or documenting project history to ensure consistent release notes and reduce manual formatting work.