Execute the release workflow for Kimi Code CLI packages.
Sample plugin demonstrating the Skills + Tools model. Includes a Python tool (greeting) and a TypeScript tool (calculator).
针对 Kimi Code CLI 的新增或变更功能，规划并执行可重复的端到端冒烟测试。从 git diff 推断功能边界，读取相关文档和代码，设计测试 prompt，以 --print 非交互模式运行本地 CLI，检查进程退出码和 session 产物，总结预期与实际行为之间的差异。发现问题时自动启动多路并行探查以定位根因。
Spawn and manage multiple Codex CLI agents via tmux to work on tasks in parallel. Use whenever a task can be decomposed into independent subtasks (e.g. batch triage, parallel fixes, multi-file refactors). When codex and tmux are available, prefer this over the built-in Task tool for parallelism.
Audit all git worktrees in the current project. Use when the user asks about worktree status, which branches are merged, which have uncommitted changes, or which worktrees can be safely cleaned up.
Sync Rust implementation with Python changes (exclude UI/login) by reviewing recent changes, mapping modules, porting logic, and updating tests.
| name | gen-changelog |
| description | Generate changelog entries for code changes. |
Generate changelog entries for changes on the current branch relative to main, then sync to the docs site.
git log main..HEAD --oneline + git diff main..HEAD --stat.## Unreleased in CHANGELOG.md using the prefix table below. For changes scoped to a subpackage under packages/ or sdks/, also update that subpackage's CHANGELOG.md — subpackage CHANGELOGs follow their own prefix conventions (e.g. packages/kosong/CHANGELOG.md uses provider prefixes like Kimi: / Anthropic:); only the root CHANGELOG follows the table below.node docs/scripts/sync-changelog.mjs.## 未发布 in docs/zh/release-notes/changelog.md. Use the full-width colon ：. Follow docs/AGENTS.md terminology.## Unreleased in docs/en/release-notes/breaking-changes.md with Affected + Migration subsections, and under ## 未发布 in docs/zh/release-notes/breaking-changes.md with 受影响 + 迁移 subsections.- <Prefix>: <verb-led sentence, readable standalone> — <optional rationale / before-after / migration>
; also, ; and, or nested em-dashes. Two changes = two bullets.Fix … / Add … / Switch … / Bump ….Lib: for SDK-facing changes.| 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.
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.