skills.rest
Wyl-cmd
Wyl-cmdCOMMUNITY
Explore all skills by this author →
GitHub

release

Automates the version bump and release workflow for Kimi Code CLI packages.

6|Updated Jan 31, 2026
Search Tags:#changelog#pull request#uv#release#monorepo#version bump#git tag
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill release-wyl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill release-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a release across multiple interdependent packages (kimi-cli, kimi-code, kagent) involves many error-prone manual steps: checking changes since the last tag, syncing versions across pyproject.toml and Cargo.toml files, updating changelogs, and opening release PRs. This Skill turns that into a guided, repeatable workflow. ## Core Features & Use Cases - Change Detection: Checks each package under packages/, sdks/, and the repo root for changes since the last release tag. - Version Synchronization: Keeps packages/kimi-code version-synced with kimi-cli and syncs the rust/Cargo.toml workspace version with the root package. - Release PR Automation: Updates CHANGELOG.md and breaking-changes.md in both languages, runs uv sync, creates a bump branch, opens a PR with gh, and monitors it until merge. - Use Case: A maintainer wants to cut a new release of kimi-cli. The Skill walks them through confirming versions per the project versioning policy, updating all files, and handing off the final git tag command after the PR merges. ## Quick Start Run the release workflow to check for package changes since the last tag and prepare a version bump PR.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a new version of kimi-cli?▼

Run the release workflow, which checks each package for changes since the last tag, confirms new versions with you, updates pyproject.toml and changelogs, opens a PR, and after merge tells you the git tag command to finalize the release.

How does the release workflow handle versioning policy?▼

The workflow follows the project versioning policy: patch is always 0, minor is bumped for any change, and major versions change only by explicit manual decision. You confirm each new version before files are updated.

Does releasing kimi-cli also release kimi-code and kagent?▼

Yes, a single numeric tag releases kimi-cli, kimi-code, and kagent together. The workflow syncs packages/kimi-code/pyproject.toml and its kimi-cli dependency, plus the rust/Cargo.toml workspace version, to match the root package.

What files get updated during a version bump?▼

The workflow updates the relevant pyproject.toml files, rust/Cargo.toml if the root version changes, CHANGELOG.md while keeping the Unreleased header, and breaking-changes.md in both languages, then runs uv sync.

What happens if no packages changed since the last release?▼

The workflow checks each package against the last release tag and ends immediately if nothing changed, so no branch, PR, or version bump is created unnecessarily.

Related Skills

Explore More Software Engineering Skills→
vladpolewoivladpolewoi

rebase

Rebase a feature branch onto the latest base branch commits.

Community
Intermediate
kuboonkuboon
2

jsr

Automate Deno package releases to JSR with Git tags and GitHub Actions.

Community
Advanced
SimplexLabSimplexLab
392

check-release

Verify TorchJD releases via docs, PyPI installation, and API smoke tests.

Official
Advanced
mia-cxmia-cx

release

Automate software releases with versioning, changelog generation, and GitHub releases.

Official
Advanced