release

Automate end-to-end release workflows for Kimi Code CLI packages.

Updated Feb 19, 2026

Search Tags:#automation #git #workflow #versioning #documentation #release #monorepo

Ready to run

npx skills add https://github.com/chen-001/kimi-cli-plus --skill release-chen-001

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating releases across multiple packages, syncing versions, updating docs, creating branches and PRs, and communicating changes can be error-prone and time-consuming.

Core Features & Use Cases

End-to-end release orchestration: Manage version checks, branch naming, PR creation, and changelog/doc updates in a single workflow.
Cross-package synchronization: Ensure consistency of versions across packages, sdks, and repository roots during a release.
Documentation and policy enforcement: Update documentation and enforce versioning policies to meet release standards.

Quick Start

Run the release skill to start the automated release workflow.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate release workflows for a monorepo with multiple packages?▼

Automating monorepo release workflows involves coordinating version checks, branch creation, PRs, and documentation updates across packages. This skill orchestrates the entire end-to-end process to ensure version synchronization and enforce project versioning policies automatically.

Can I synchronize dependency versions across sdks and the repository root during a release?▼

Yes, synchronizing dependency versions across sdks and the repository root during a release is supported. The workflow ensures consistency of versions across all packages and automatically updates dependencies to meet project versioning standards.

What is the best way to update CHANGELOG.md and breaking-changes files during a version release?▼

The best way to update CHANGELOG.md and breaking-changes files during a release is through automated workflow orchestration. This skill automatically updates documentation, enforces versioning policies, and communicates changes to meet release standards.

Does the release automation workflow create git branches and pull requests automatically?▼

Yes, the release automation workflow creates git branches and pull requests automatically. It manages end-to-end release orchestration including branch naming, PR creation, and changelog updates in a single coordinated workflow.

Why should I use an automated release workflow instead of manual versioning for my packages?▼

Automated release workflows prevent error-prone manual coordination across multiple packages. Manually syncing versions, updating docs, and creating PRs is time-consuming, whereas automation enforces versioning policies and ensures consistency across the repository.