changelog-gen

Parse git history between two refs and generate categorized Markdown changelog entries.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jieni777/opencode-config-backup --skill changelog-gen-jieni777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/changelog-gen
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill changelog-gen-jieni777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool generates a clean, categorized CHANGELOG entry from git history, saving time and avoiding manual note writing.

Core Features & Use Cases

  • Groups commits into Added, Changed, Fixed, Removed.
  • Reads git history between two refs and outputs a Markdown-ready entry.
  • Use case: Release notes generation for software projects of any size.

Quick Start

Run npx ai-changelog --from <start> --to <end> to produce a release note for that range.

Frequently Asked Questions about changelog-gen

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

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

Generate release notes from git history by parsing commits between two references, filtering out merges, and formatting the output into categorized Markdown entries. This process reads raw git logs and groups changes into Added, Changed, Fixed, and Removed categories.

What is the best way to categorize git commits into a Markdown changelog?

Categorize git commits into a Markdown changelog by parsing the commit history between a start and end ref. The process automatically filters merge commits and groups the remaining changes into standard categories like Added, Changed, Fixed, and Removed.

Can I create reproducible release notes between any two git refs?

Yes, you can create reproducible release notes between any two git refs. The tool reads raw git logs from a specified start and end reference, ensuring the resulting Markdown changelog accurately reflects only the commits in that range.

How do I exclude merge commits from automated changelog generation?

Exclude merge commits from automated changelog generation by using a tool that reads raw git logs and explicitly filters out merges. This ensures the final Markdown release notes contain only meaningful feature and bugfix entries.

Does automated changelog generation work for software projects of any size?

Automated changelog generation works for software projects of any size. As long as the project maintains a git history between two references, the tool can parse the commits and produce a concise, categorized Markdown changelog suitable for release notes.