gen-changelog

Generate changelog entries from git diffs and update CHANGELOG.md files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates changelog entries for code changes by analyzing the differences between the current branch and main, and keeps the documentation site up to date.

Core Features & Use Cases

  • Analyze git history and diffs to produce release notes for a branch.
  • Update the root CHANGELOG.md under the Unreleased section and propagate changes to sub-packages' CHANGELOG.md when applicable.
  • Synchronize English and Chinese release notes in docs to reflect the latest changes.

Quick Start

Generate a changelog for the current branch and update the Unreleased section in the root CHANGELOG, propagating to package changelogs and syncing docs as needed.

Frequently Asked Questions about gen-changelog

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

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

To generate release notes from git history, analyze the differences between your current branch and main, then produce a concise changelog entry summarizing the code changes for that branch.

Can I update the Unreleased section in CHANGELOG.md without manual editing?

You can update the Unreleased section in CHANGELOG.md automatically by analyzing the diff between the current branch and main, appending the generated changelog entry directly into the root file.

How do I sync English and Chinese release notes in docs after a code change?

To sync English and Chinese release notes in docs, generate the changelog entry from the branch diff and propagate the updated text into both language versions of the documentation site.

Does this changelog automation work for monorepos with sub-packages?

For monorepos with sub-packages, the automation propagates the generated changelog entry from the root CHANGELOG.md into the respective sub-packages' CHANGELOG.md files when applicable.

What is the best way to keep documentation site release notes in sync with code changes?

The best way to keep documentation release notes in sync is to analyze the git diff against main, generate a concise changelog entry, and update both the root CHANGELOG.md and the localized docs simultaneously.