release

Automate multi-package release workflows for Kimi Code CLI.

11.1k|1.3k|Updated Oct 15, 2025

Search Tags:#automation #git #workflow #versioning #release #ci-cd #multi-package

Ready to run

npx skills add https://github.com/MoonshotAI/kimi-cli --skill release-moonshotai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/MoonshotAI/kimi-cli/tree/main/.agents/skills/release
Command: npx skills add https://github.com/MoonshotAI/kimi-cli --skill release-moonshotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release automation coordinates multi-package version bumps, changelog updates, and repository synchronization to ensure consistent, error-free releases across Kimi Code CLI.

Core Features & Use Cases

Orchestrates multi-package version bumps, changelog updates, and synchronization across packages and root.
Creates dedicated release branches, opens pull requests, and post-merge tagging to streamline the release lifecycle.
Ensures consistency by updating pyproject.toml, Cargo.toml, and related files across packages during release.

Quick Start

Run the release workflow to start the end-to-end release process for all Kimi Code CLI packages.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate multi-package releases for CLI projects?▼

Multi-package release automation is achieved by orchestrating a deterministic workflow that detects changes, updates version strings in pyproject.toml and Cargo.toml, syncs dependencies, and generates changelogs across all packages. This ensures consistency and eliminates manual error during the release lifecycle.

How do I sync dependencies and version strings across multiple packages?▼

To sync dependencies and version strings, the release workflow automatically detects changes across the packages directory and updates pyproject.toml, Cargo.toml, and related files. It ensures all root and sub-packages maintain consistent versioning and dependency alignment before creating a release branch.

Can I use this workflow to create release branches and monitor pull requests?▼

Yes, the release workflow creates dedicated release branches, opens pull requests, and monitors PR status. After the PR is merged, it automatically performs post-merge tagging to finalize the release lifecycle across the repository.

What is the best way to update changelogs and docs during a CI-CD release?▼

The best way to update changelogs and docs during a CI-CD release is using a deterministic workflow that generates documentation and updates changelog files automatically. This happens after version strings are confirmed and synced, ensuring all generated docs reflect the latest multi-package changes.

Does this release process work with both Python and Rust packages?▼

Yes, the release process works with both Python and Rust packages by updating pyproject.toml and Cargo.toml respectively. It orchestrates version bumps and dependency synchronization across all detected packages to ensure consistent, error-free releases regardless of the language.

When do I need a deterministic workflow for versioning and releases?▼

A deterministic workflow for versioning and releases is needed when managing a multi-package repository where consistency is critical. It prevents human error by applying a strict sequence of steps to detect changes, confirm versions, update files, sync dependencies, and handle post-merge tagging.