Gen Changesets
Use when generating changesets in the kimi-code repository, deciding whether to write...
Install
npx skills add MoonshotAI/kimi-code --skill gen-changesets -g -a claude-code -y- Repository
- MoonshotAI/kimi-code8.1k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,021 tokens
- Runs scripts
- No, instructions only
What it does
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.
Generate Changesets
The only user-facing published package is the CLI: @moonshot-ai/kimi-code. All other @moonshot-ai/* packages (sdk, kosong, 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.
