gen-changelog
Generates, formats, and syncs changelog entries based on git history and project-specific conventions.
Install
mkdir -p .claude/skills/gen-changelog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2330" && unzip -o skill.zip -d .claude/skills/gen-changelog && rm skill.zipInstalls to .claude/skills/gen-changelog
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generate changelog entries for code changes.Key capabilities
- →Parse git logs to generate standardized changelog entries
- →Sync changelog updates to documentation sites
- →Manage breaking change records with migration instructions
- →Translate release notes into Chinese
- →Enforce prefix-based categorization for changes
How it works
The agent inspects git logs and diffs to generate bulleted entries, which are then categorized by prefix and synced to both English and Chinese documentation files.
Inputs & outputs
When to use gen-changelog
- →Generating release notes from git history
- →Syncing changelogs across subpackages
- →Documenting breaking changes
About this skill
Generate changelog entries for changes on the current branch relative to main, then sync to the docs site.
Steps
- Inspect:
git log main..HEAD --oneline+git diff main..HEAD --stat. - Edit root CHANGELOG: add bullets under
## UnreleasedinCHANGELOG.mdusing the prefix table below. For changes scoped to a subpackage underpackages/orsdks/, also update that subpackage'sCHANGELOG.md— subpackage CHANGELOGs follow their own prefix conventions (e.g.packages/kosong/CHANGELOG.mduses provider prefixes likeKimi:/Anthropic:); only the root CHANGELOG follows the table below. - Sync English docs:
node docs/scripts/sync-changelog.mjs. - Translate to Chinese: hand-write equivalents under
## 未发布indocs/zh/release-notes/changelog.md. Use the full-width colon：. Followdocs/AGENTS.mdterminology. - Breaking changes: if any, add a section under
## Unreleasedindocs/en/release-notes/breaking-changes.mdwith Affected + Migration subsections, and under## 未发布indocs/zh/release-notes/breaking-changes.mdwith 受影响 + 迁移 subsections.
Entry format
- <Prefix>: <verb-led sentence, readable standalone> — <optional rationale / before-after / migration>
- First sentence stands alone — readers should know after one sentence whether the bullet matters to them.
- One change per bullet. No
; also,; and, or nested em-dashes. Two changes = two bullets. - Verb-led:
Fix …/Add …/Switch …/Bump …. - User-meaningful only. No internal refactors, test churn, or CI tweaks — except
Lib:for SDK-facing changes.
Prefixes — pick from this list, do not invent new ones
| Prefix | Scope |
|---|---|
Shell | Interactive TUI: keys, status bar, slash commands, terminal rendering |
Web | kimi web |
Vis | kimi vis tracing visualizer |
CLI | Top-level flags, subcommands, --print / --yolo / --afk |
ACP | Zed / JetBrains and other ACP integrations |
Core | Agent runtime, step loop, approval, quota, turns, background tasks |
Tool | Any built-in tool; name the specific tool in the body (ReadFile, Grep, Todo, Plan, …) |
Skill | Skill discovery/loading, Flow, Loop (always singular — not Skills:) |
MCP | MCP server integration |
Plugin | Plugin system, kimi plugin subcommands |
LLM | Provider-agnostic or cross-provider; name the provider in the body (Kimi / Anthropic / OpenAI / DeepSeek …). Do not create per-provider prefixes |
Kosong | Changes to the kosong LLM abstraction layer surfaced in the root CHANGELOG (the subpackage's own CHANGELOG uses provider prefixes) |
Wire | Wire protocol events, version |
Auth | OAuth, token refresh, /login |
Config | Config schema, env vars |
Lib | SDK-facing API changes |
Build | Nix / Rust / Python / packaging |
When unsure, match an existing entry of the same kind. Prefer this list; if you genuinely need a new prefix, raise it with maintainers and update this table in the same PR so the convention stays single-sourced.
Ordering: within each version, group bullets by prefix in the order of the table above. Order within a prefix is free — keep the development order.
Highlights
Starting from the next release, add **Highlights**: … under each version header (1–3 items most users will notice); mirror it as **亮点**：… in Chinese. Skip on releases that are only internal or Lib:. Highlights summarize — every highlighted item still needs its full bullet below. Do not backfill historical versions.
When not to use it
- →Projects not using git for version control
- →Repositories without a defined CHANGELOG.md structure
Prerequisites
Limitations
- →Requires manual translation for Chinese release notes
- →Limited to specific prefix categories defined in the source
How it compares
This workflow enforces strict formatting and prefix conventions across root and subpackage changelogs, replacing manual log parsing and documentation updates.
Compared to similar skills
gen-changelog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gen-changelog (this skill) | 4 | 3mo | No flags | Beginner |
| prepare-changelog | 6 | 7mo | Review | Beginner |
| workthrough | 10 | 8mo | Review | Beginner |
| generate-release-notes | 7 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by MoonshotAI
View all by MoonshotAI →You might also like
prepare-changelog
nextest-rs
Guidelines for preparing changelog entries for nextest releases following Keep a Changelog format
workthrough
bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
generate-release-notes
teambit
Generate comprehensive release notes for Bit from git commits and pull requests. Use when creating release notes, building changelogs, documenting version releases, or preparing a new Bit release.
changelog-generator
ComposioHQ
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
release-note-generation
microsoft
Toolkit for generating PowerToys release notes from GitHub milestone PRs or commit ranges. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare release documentation, request Copilot reviews for PRs, update README for a new release, manage PR milestones, or collect PRs between commits/tags. Supports PR collection by milestone or commit range, milestone assignment, grouping by label, summarization with external contributor attribution, and README version bumping.
doc-check
coder
Checks if code changes require documentation updates