release

Coordinate version checks, file updates, and PR creation for Kimi Code CLI releases.

Updated Feb 8, 2026

Search Tags:#automation #workflow #devops #versioning #CI/CD #release #package-management

Ready to run

npx skills add https://github.com/Zidane786/os-coding-agents --skill release-zidane786

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the release workflow for Kimi Code CLI packages, reducing manual steps and ensuring version consistency across packages.

Core Features & Use Cases

Orchestrates the full release process by detecting changes, validating versions, updating metadata, and opening pull requests.
Synchronizes root and package versions (kimi-code, kagent) and updates CHANGELOGs, docs, and breaking-change notes to support coordinated releases.
Supports multi-package releases with a unified branching strategy and post-merge tagging guidance.

Quick Start

Initiate the release workflow to detect changes, confirm new versions, apply updates, and open a pull request across all affected packages.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate CLI package releases for versioning and changelog updates?▼

Automating CLI package releases involves coordinating version checks, file updates, and PR creation to synchronize versions and generate consistent changelogs, docs, and tags. This reduces manual steps and ensures version consistency across packages.

What is the best way to manage multi-package versioning in a CI/CD workflow?▼

The best way to manage multi-package versioning is using a unified branching strategy that detects changes, validates versions, and updates metadata across packages. This supports coordinated releases with synchronized root and package versions.

How does post-merge tagging work for synchronized package releases?▼

Post-merge tagging provides guidance on applying tags after a release pull request is merged. It ensures that root and package versions remain consistent and that breaking-change notes are properly documented during the release workflow.

Do I need to read AGENTS.md and release workflow files to automate package releases?▼

Yes, reading AGENTS.md and release workflow files is required to automate package releases. This ensures the automation correctly manages branching, validates versions, and coordinates updates across affected packages and root directories.

Can I synchronize changelogs and breaking-change notes across multiple packages during a release?▼

Yes, you can synchronize changelogs and breaking-change notes across multiple packages during a release. The automation updates CHANGELOGs, docs, and breaking-change notes to support coordinated releases across root and package directories.

What are the limitations of automating release workflows for CLI packages?▼

Limitations include relying on a unified branching strategy and requiring manual oversight for post-merge tagging. The automation focuses on coordinating version checks and PR creation but may need intervention for complex multi-package edge cases.