gen-changelog

Generate structured changelog entries from git diffs between branches.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Zidane786/os-coding-agents --skill gen-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-changelog
Source: https://github.com/Zidane786/os-coding-agents/tree/main/kimi-cli/.agents/skills/gen-changelog
Command: npx skills add https://github.com/Zidane786/os-coding-agents --skill gen-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you automatically generate changelog entries from code changes between your current branch and main, and keeps documentation in sync across the project.

Core Features & Use Cases

  • Analyze git history and diffs to produce concise, user-friendly changelog items.
  • Update the root CHANGELOG.md under the Unreleased section and propagate updates to sub-packages (packages/ or sdks/).
  • Sync generated entries to the documentation site using the provided docs script.

Quick Start

Run the changelog generator to analyze branch differences and update the unreleased changelog accordingly.

Frequently Asked Questions about gen-changelog

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

FAQPage Schema
How do I generate a changelog from git branch differences?

To generate a changelog from git branch differences, you analyze the code changes between your current branch and main to produce structured changelog entries. This updates the root CHANGELOG.md under the Unreleased section automatically.

Can I propagate changelog updates to multiple sub-packages?

Yes, you can propagate changelog updates to multiple sub-packages. The generated entries update the root CHANGELOG.md and sync to sub-packages located in directories like packages/ or sdks/.

How do I sync generated changelog entries to a documentation site?

To sync generated changelog entries to a documentation site, you use the provided docs sync script. This script publishes the updated changelog items to the documentation site after analyzing the git history.

Do I need a conventional changelog structure to automate release notes?

Yes, you need a conventional changelog structure to automate release notes effectively. The generation process assumes this structure to analyze git diffs and populate the Unreleased section accurately.

What is the best way to automate changelog generation for software projects?

The best way to automate changelog generation for software projects is to analyze git history and diffs between branches. This produces concise, user-friendly changelog items and keeps documentation synced across multiple packages.