release

Automate multi-package release workflows with versioning, changelog updates, and PR creation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hvrryh-web/RadiantX --skill release-hvrryh-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/hvrryh-web/RadiantX/tree/main/.agents/skills/release
Command: npx skills add https://github.com/hvrryh-web/RadiantX --skill release-hvrryh-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing multiple Kimi Code CLI packages is error-prone and time-consuming due to manual versioning, changelog maintenance, and PR orchestration. This Skill automates the end-to-end release process to reduce mistakes and accelerate delivery.

Core Features & Use Cases

  • Automated versioning coordination: Sync versions across packages, root, and language-specific manifests.
  • Changelog automation: Maintain Unreleased sections and generate changelog entries for each release.
  • Branch and PR workflow: Create feature branches and open PRs automatically for changed packages.

Quick Start

Run the release workflow to automatically align versions, update changelogs, and open a PR for each changed package.

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 multi-package repositories?

Automate release workflows by coordinating versioning, changelog updates, and branch/PR automation across packages, sdks, and root directories. This ensures consistent version synchronization and automatically opens a pull request for each changed package.

How do I sync versions across Python and Rust packages in a monorepo?

Sync versions across Python and Rust packages by enforcing automated updates to pyproject.toml and Cargo.toml. The automation aligns versions across language-specific manifests, root configurations, and sub-packages to prevent manual versioning errors.

Does automated release automation preserve Unreleased sections in CHANGELOG.md?

Automated release automation preserves the Unreleased section in CHANGELOG.md while generating new changelog entries for each release. This maintains a consistent changelog history without losing pending changes queued for future releases.

Can I use automated branch and PR creation for changed packages in CI/CD?

Automated branch and PR creation works within CI/CD pipelines by generating a feature branch and opening a pull request for each changed package. This orchestrates multi-package releases without manual Git workflow intervention.

What is the best way to coordinate versioning for Kimi CLI packages?

Coordinate versioning for Kimi CLI packages by automating the end-to-end release process, which aligns manifests across packages, sdks, and root. This reduces manual mistakes and accelerates delivery by synchronizing artifacts across languages.