haomingz understand: |md
Understand the release automation by reading AGENTS.md and
.github/workflows/release*.yml.
|
check_changes: |md
Check each package under packages/, sdks/, and repo root for changes since the
last release (by tag). Note packages/kimi-code is a thin wrapper and must stay
version-synced with kimi-cli.
|
has_changes: "Any packages changed?"
confirm_versions: |md
For each changed package, confirm the new version with the user. Follow the
project versioning policy: patch is always 0, bump minor for any change,
major only changes by explicit manual decision.
|
update_files: |md
Update the relevant pyproject.toml (and rust/Cargo.toml if root version changes),
CHANGELOG.md (keep the Unreleased header), and breaking-changes.md in both languages.
|
root_change: "Is the root package version changing?"
sync_kimi_code: |md
Sync packages/kimi-code/pyproject.toml version and dependency
`kimi-cli==<version>`.
|
sync_kagent: |md
Sync rust/Cargo.toml workspace version to match the root package version.
|
uv_sync: "Run uv sync."
gen_docs: |md
Follow the gen-docs skill instructions to ensure docs are up to date.
|
new_branch: |md
Create a new branch `bump-<package>-<new-version>` (multiple packages can share
one branch; name it appropriately).
|
open_pr: |md
Commit all changes, push to remote, and open a PR with gh describing the
updates.
|
monitor_pr: "Monitor the PR until it is merged."
post_merge: |md
After merge, switch to main, pull latest changes, and tell the user the git
tag command needed for the final release tag (they will tag + push tags). Note:
a single numeric tag releases kimi-cli, kimi-code, and kagent together.
|
BEGIN -> understand -> check_changes -> has_changes
has_changes -> END: no
has_changes -> confirm_versions: yes
confirm_versions -> update_files -> root_change
root_change -> sync_kimi_code: yes
root_change -> uv_sync: no
sync_kimi_code -> sync_kagent
sync_kagent -> uv_sync
uv_sync -> gen_docs -> new_branch -> open_pr -> monitor_pr -> post_merge -> END
Release by haomingz · c8c22b0
npx skillmds@latest add haomingz/release File contents
---name: releasedescription: Execute the release workflow for Kimi Code CLI packages.---```d2understand: |md Understand the release automation by reading AGENTS.md and .github/workflows/release*.yml.|check_changes: |md Check each package under packages/, sdks/, and repo root for changes since the last release (by tag). Note packages/kimi-code is a thin wrapper and must stay version-synced with kimi-cli.|has_changes: "Any packages changed?"confirm_versions: |md For each changed package, confirm the new version with the user. Follow the project versioning policy: patch is always 0, bump minor for any change, major only changes by explicit manual decision.|update_files: |md Update the relevant pyproject.toml (and rust/Cargo.toml if root version changes), CHANGELOG.md (keep the Unreleased header), and breaking-changes.md in both languages.|root_change: "Is the root package version changing?"sync_kimi_code: |md Sync packages/kimi-code/pyproject.toml version and dependency `kimi-cli==<version>`.|sync_kagent: |md Sync rust/Cargo.toml workspace version to match the root package version.|uv_sync: "Run uv sync."gen_docs: |md Follow the gen-docs skill instructions to ensure docs are up to date.|new_branch: |md Create a new branch `bump-<package>-<new-version>` (multiple packages can share one branch; name it appropriately).|open_pr: |md Commit all changes, push to remote, and open a PR with gh describing the updates.|monitor_pr: "Monitor the PR until it is merged."post_merge: |md After merge, switch to main, pull latest changes, and tell the user the git tag command needed for the final release tag (they will tag + push tags). Note: a single numeric tag releases kimi-cli, kimi-code, and kagent together.|BEGIN -> understand -> check_changes -> has_changeshas_changes -> END: nohas_changes -> confirm_versions: yesconfirm_versions -> update_files -> root_changeroot_change -> sync_kimi_code: yesroot_change -> uv_sync: nosync_kimi_code -> sync_kagentsync_kagent -> uv_syncuv_sync -> gen_docs -> new_branch -> open_pr -> monitor_pr -> post_merge -> END```
haomingz/kimi-skills/tree/main/skills/release commit c8c22b0482
Frequently asked questions
Run npx skillmds@latest add haomingz/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Execute the release workflow for Kimi Code CLI packages. It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
haomingz (@haomingz) published this skill. Their other Agent Skills are listed on their SkillMD profile.