release

Analyze version sources and CI rules to orchestrate repository releases.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill release-xz1220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/release
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill release-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork and inconsistency in performing releases by analyzing a repository’s version sources, CI publishing rules, and changelog conventions, then guiding you through a validated release process.

Core Features & Use Cases

  • Release rule discovery and caching: Inspects the repo to infer release triggers, version bump locations, test gates, and publishing targets, then stores the results in .omk/RELEASE_RULE.md for later use.
  • CI-aware delta refresh: Re-analyzes only when relevant workflow/CI files change since the last analysis, helping keep release rules up to date without doing a full re-scan every time.
  • End-to-end release execution guidance: Chooses the next version (major/minor/patch or explicit semver), produces a pre-release checklist, helps draft release notes, and walks through bumping, tagging, committing, pushing, and validating outcomes.

Quick Start

Run the release skill for your project by asking: /oh-my-kimi:release minor

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub Actions releases for npm, PyPI, and Docker?

Automate GitHub Actions releases by analyzing CI publishing rules, validating test gates, and orchestrating version bumping, tagging, and pushing for npm, PyPI, and Docker. The process detects publish triggers and writes reusable rules to .omk/RELEASE_RULE.md.

What is the best way to determine semantic versioning bumps for a new release?

Determine semantic versioning bumps by analyzing repository version sources and CI workflows. This process chooses the next major, minor, or patch version based on detected changes and validates it against established release rules before tagging.

How does CI-aware delta refresh work for updating release rules?

CI-aware delta refresh updates release rules by re-analyzing only when relevant workflow or CI files change since the last analysis. This prevents full repository re-scans while keeping release triggers and version bump locations current.

Can I use this release management process for first-time publishing workflows?

Yes, this release management process applies to first-time publishing workflows and follow-up releases with cached rules. It detects version fields and release automation from scratch, guiding you through initial setup and subsequent validated executions.

How do I generate a changelog and pre-release checklist before publishing?

Generate a changelog and pre-release checklist by analyzing repository conventions and CI publishing rules. The process drafts release notes, validates test gates, and walks you through committing, pushing, and validating the final outcomes.