gen-changesets
Use when generating changesets in the kimi-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 8.2k
- Forks
- 1.4k
01 前言 Front Matter
- name
- gen-changesets
- description
- Use when generating changesets in the kimi-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.
03 SKILL.md 正文
Generate Changesets
The only user-facing published package is the CLI: @moonshot-ai/kimi-code. All other @moonshot-ai/* packages (sdk, oauth, telemetry, and so on) are internal.
1. Whether to Write
Rule of thumb: if users cannot perceive the change, write no changeset. A changeset is a user-facing changelog entry, not a shipping gate — internal changes merged to main ship with the next release anyway, so skipping loses nothing.
Do not write:
- Docs-only or tests-only changes that never enter the shipped artifact.
- Changes internal to core/server packages — architecture, protocols, refactors, config/journal/wire mechanics — unless they fix a bug users care about.
- When you are unsure whether users can perceive a change, ask first.
Do write: user-perceivable new features or behavior changes, and internal-package changes that fix a user-useful bug or change CLI output/behavior (list @moonshot-ai/kimi-code for those).
2. What to Write
Create a short kebab-case file under .changeset/:
---
"@moonshot-ai/kimi-code": patch
---
Fix occasional loss of tool call results in long conversations.
Wording:
- One short, user-facing English sentence that states only what changed. Drop trailing clauses that explain the cause, the benefit, or the mechanism.
- When a default flips or an existing behavior is removed, name the behavior users lose, not only the new default. State the escape hatch if one exists, e.g.
Stop hot-reloading config, skills, and AGENTS.md by default; set [watch] enabled = true or KIMI_CODE_WATCH=1 to turn it back on.; if there is none, say plainly that the old behavior is no longer available. - New features: say plainly what it is plus one line on how to use it, e.g.
Add the /foo slash command to list active sessions. Run /foo to see them. - Experimental features: also state how to enable them (the flag, config key, or env var).
- No file, class, or function names, and no PR numbers. No vague words like refactor, optimize, or improve. No real internal identifiers — use neutral placeholders such as
example.comorYOUR_API_KEY. - Internal packages' own changelogs (such as the sdk) are not curated for end users — write those entries honestly and technically.
- One logical change per changeset; split unrelated changes into separate files.
3. Bump Level
patch: bug fixes, small improvements, configuration additions to existing features — when in doubt, use this.minor: a real new capability users could not do before (a new slash command, a new subcommand, a new mode).major: never write it. If you think a change qualifies, stop and ask the user; without explicit approval fall back tominor, or topatchifminoris also unclear.
4. Which Package
- An internal change enters the CLI bundle and is user-perceivable → list
@moonshot-ai/kimi-code. - An internal change does not enter the CLI or is not user-perceivable → write nothing; if it is written, list only that internal package.
- Never mix packages ignored in
.changeset/config.jsonwith non-ignored packages in one frontmatter. - pi-tui exception: pi-tui-only changes list
@moonshot-ai/pi-tui; if the same change is also visible to CLI users, write a separate CLI changeset (two files, never mixed). - The vis packages never appear in a changeset.
5. Workflow
- Run
git status/git diff --name-onlyto see which packages actually changed. - Apply section 1; if no changeset is needed, stop.
- Pick the package and the bump, and write the one sentence.
- Show the changeset text to whoever requested the work and get their confirmation before committing.
- Do not guess at changes you do not understand: finish the parts that are clear, then list what is unclear and ask whether you may dig into the code.
Before a release, review the accumulated .changeset/ entries and delete the non-user-facing ones — the release PR regenerates from .changeset/ on the selected release branch, so deleting a file removes its changelog entry without touching shipped code.
04 同仓库更多 Skills
golden-skill
Golden fixture skill
tools
暂无简介
review
Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.
consolidate
Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.
sub-skill
Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.
write-tui
Use when writing or modifying the kimi-code terminal UI in apps/kimi-code/src/tui — components, dialogs/selectors, slash commands, themes, streaming render, or the KimiTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction/visual spec (DESIGN.md).