gen-changelog

Generate changelog entries from git branch changes and sync them to documentation sites.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill gen-changelog-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-changelog
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/.agents/skills/gen-changelog
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill gen-changelog-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing changelog entries for every code change is tedious and error-prone, especially when entries must be kept consistent across a root CHANGELOG, sub-package changelogs, and bilingual documentation sites. ## Core Features & Use Cases - Git-based change analysis: Inspects commits and diffs between the current branch and main to identify user-facing changes. - Multi-file changelog updates: Adds entries to the root CHANGELOG.md, sub-package changelogs under packages/ or sdks/, and both English and Chinese documentation changelogs. - Breaking change tracking: Records breaking changes in dedicated breaking-changes documents with migration notes in both languages. - Use Case: After merging a feature branch that renames a CLI option, run this Skill to generate the changelog entry, sync it to the English docs via the sync script, add the Chinese translation, and document the breaking change with migration guidance. ## Quick Start Generate changelog entries for all changes on my current branch compared to main and sync them to the documentation site.

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 commits?

Run git log main..HEAD --oneline and git diff main..HEAD --stat to review all changes on your branch, then write user-facing entries under the Unreleased section of CHANGELOG.md following the existing category-prefix format.

How to keep changelogs in sync across multiple packages?

Update the root CHANGELOG.md first, then add corresponding entries to each affected sub-package changelog under packages/ or sdks/. Use a sync script to propagate the root changelog to documentation sites automatically.

Should internal refactoring be included in a changelog?

No, changelogs should only contain changes meaningful to users, such as new features, bug fixes, and behavior changes. Pure internal refactoring, code cleanup, and test updates should be omitted.

How do I document breaking changes in release notes?

Add entries to a dedicated breaking-changes document under the Unreleased section, following the format of version heading, subsection, affected functionality, and migration instructions. Document them in every supported language.

What git command shows changes between a branch and main?

Use git log main..HEAD --oneline to list commits unique to your branch and git diff main..HEAD --stat to see which files changed. Together these give a complete picture for writing changelog entries.