gen-changelog

Original：🇨🇳 Chinese

Translated

Generate changelog entries for code changes.

1installs

Added on2026-02-25

NPX Install

npx skill4agent add moonshotai/kimi-cli gen-changelog

Generate changelog entries based on the changes of the current branch relative to the main branch, and sync them to the documentation site.

Analyze Changes: Check

git log main..HEAD --oneline

and

git diff main..HEAD --stat

to understand all changes.

Update the Source CHANGELOG: Add entries under
```
## Unreleased
```
in the root directory's
```
CHANGELOG.md
```
; if the changes belong to sub-packages under
```
packages/
```
or
```
sdks/
```
, also update the
```
CHANGELOG.md
```
in the corresponding directory.

Sync English Documentation Changelog: Run

node docs/scripts/sync-changelog.mjs

to sync the root

CHANGELOG.md

to

docs/en/release-notes/changelog.md

.

Update Chinese Documentation Changelog: Add corresponding Chinese translated entries under
```
## Unreleased
```
in
```
docs/zh/release-notes/changelog.md
```
, following the existing format and terminology specifications (refer to the glossary and typesetting guidelines in
```
docs/AGENTS.md
```
).
Breaking Changes (if applicable): If the changes include breaking changes (such as removing/renaming options, changing default behaviors, migrating configuration formats, etc.), you also need to add corresponding entries under
```
## Unreleased
```
in
```
docs/en/release-notes/breaking-changes.md
```
and
```
docs/zh/release-notes/breaking-changes.md
```
, following the existing format (version title + section + affected/migration instructions).

Follow the format of the existing CHANGELOG for entry style:
```
- Category: Description
```
(e.g.,
```
- Core: ...
```
,
```
- Web: ...
```
).
Only write changes meaningful to users; do not include pure internal refactoring.
Chinese translations should follow the terminology mapping and typesetting guidelines in
```
docs/AGENTS.md
```
.