release

Analyze version sources and CI workflows to derive release rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork from releasing software by inspecting your repository and CI to determine how to bump versions, run tests, publish artifacts, and create release notes.

Core Features & Use Cases

  • Repo-aware release rule discovery: Analyzes version sources, publishing targets (npm/PyPI/Cargo/Docker), triggers (tags/workflows/branches), test gates, and changelog/release-notes conventions.
  • Cached rules for faster reruns: Stores derived guidance in .omc/RELEASE_RULE.md and detects workflow changes to refresh only when needed.
  • End-to-end release walkthrough: Guides version selection, pre-release checklist, release notes drafting, and the operational steps to bump, test, commit, tag, and push.

Quick Start

Ask for a release plan with the desired bump by telling the AI: run /oh-my-claudecode:release patch.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic versioning and release steps across different publishing targets?

Automated release planning derives repo-specific release rules by inspecting version sources and CI workflows, generating cached guidance in .omc/RELEASE_RULE.md to standardize version bumping, test gating, changelog preparation, and git tagging operations.

What's the best way to prepare changelogs and release notes based on my existing repository conventions?

Release rule discovery analyzes your repository's changelog and release-notes conventions alongside CI workflows, generating cached guidance that drives consistent release notes drafting during the operational release walkthrough.

How do I run a test-gated publishing workflow for a new version bump?

Test-gated publishing is executed by validating semantic version inputs, applying derived release rules to run pre-release checklists, and walking through operational steps to bump, test, commit, tag, and push to common registry setups.

Does this release automation approach work with Cargo, PyPI, and Docker registries?

Release rule discovery supports common registry setups including npm, PyPI, Cargo, and Docker by inspecting repository configuration and CI workflows to determine appropriate version bumping, tagging, and publishing triggers.

Why do I need a cached release rule file for repeated software releases?

Cached release rules stored in .omc/RELEASE_RULE.md accelerate repeated releases by avoiding full repository re-analysis, refreshing automatically only when underlying CI workflow changes are detected.

When should I refresh cached release rules instead of generating new ones?

Cached release rules require refreshing when CI workflow changes are detected, while standard reruns utilize the existing .omc/RELEASE_RULE.md guidance to bypass redundant repository analysis and accelerate the release process.