changelog-generator

Parse Git history to generate Markdown changelogs in Keep a Changelog format.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill changelog-generator-arry8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Arry8/openclaw-edge/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill changelog-generator-arry8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning Git history into structured release notes, reducing manual effort and errors.

Core Features & Use Cases

  • Parse Conventional Commits and group changes by type for clear release notes.
  • Generate Keep a Changelog-compliant markdown and customizable release notes.
  • Support range-based analysis (between tags, since last tag, or last N commits) for precise reporting.

Quick Start

Generate a Keep a Changelog-compliant release notes for the changes between two git tags or since the last tag.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate release notes from git history using Conventional Commits?

Generate release notes from git history by parsing Conventional Commits to group changes by type, producing structured Keep a Changelog-compliant markdown outputs.

Can I extract changelog entries between two specific git tags?

Yes, you can extract changelog entries between two specific git tags. Range-based analysis supports generating release notes between tags, since the last tag, or for the last N commits.

Does the changelog generator output Keep a Changelog compliant markdown?

Yes, the changelog generator outputs Keep a Changelog compliant markdown. It parses git history and formats structured release notes into this standard markdown format for easy customization.

Do I need git installed to parse commit history for markdown release notes?

Yes, you need git installed to parse commit history for markdown release notes. The generator requires git to access repository history and extract commit messages for changelog generation.

What is the best way to automate markdown changelog creation from commit messages?

The best way to automate markdown changelog creation is parsing Conventional Commits directly from git history. This approach groups changes by type and outputs Keep a Changelog-compliant markdown automatically.