omk-flow-release

Automate version bumps, changelog updates, and release verification in CI/CD workflows.

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-flow-release
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/omk-flow-release
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the risk of shipping broken or undocumented releases by enforcing a disciplined release process that updates versions, changelogs, and deployment health checks.

Core Features & Use Cases

  • Version bump from evidence: Determines the required version change by analyzing the diff and commit history to align release semantics with actual changes.
  • Changelog and quality gates: Updates CHANGELOG.md and runs full quality gates to prevent regressions before tagging.
  • Tag, deploy, and verify: Creates a git tag, optionally deploys, and verifies deployment health to confirm the release is operational.

Use case example: You merge multiple changes into main, need a consistent version bump, and want an automated system that updates the changelog, blocks bad builds, tags the release, deploys (when configured), and confirms the service is healthy.

Quick Start

Run the omk-flow-release skill to bump the version, update CHANGELOG.md, run quality gates, tag the release, deploy if configured, and verify deployment health.

Frequently Asked Questions about omk-flow-release

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

FAQPage Schema
How do I automate version bumps and changelog updates from commit history?

To automate version bumps and changelog updates, this Skill analyzes your git diff and commit history to determine the required semantic version change and automatically updates CHANGELOG.md before running quality gates.

What is the best way to block bad builds during a CI/CD release?

The best way to block bad builds is to enforce sequential quality gates that abort the release and require fixes when checks fail, ensuring only verified code proceeds to a git tag and deployment.

How does deployment verification work after tagging a release?

Deployment verification works by running deterministic health checks after the optional deployment step to confirm the released service is operational, completing the release process only if runtime health is verified.

Can I deploy and verify runtime health without manual intervention?

Yes, you can deploy and verify runtime health automatically if deployment is configured, as the process applies deterministic verification steps immediately after creating a git tag to confirm the service is operational.

What happens when quality gates fail during an automated software release?

When quality gates fail during an automated software release, the process triggers an abort-and-fix behavior, halting the version bump, changelog update, and git tag creation until the failing checks are resolved.

Do I need external dependencies to run automated release quality gates?

No external dependencies are required to run automated release quality gates, as the Skill operates independently to analyze commit history, bump versions, and update the changelog before tagging.