release

Name: release
Availability: InStock
Author: dropsyoon

Guide repository releases by analyzing version sources, CI triggers, and test gates.

Updated Apr 17, 2026

Search Tags:#changelog #versioning #release #publish #semver #tagging #ci workflow

Ready to run

npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill release-dropsyoon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/release
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill release-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the uncertainty of how to release a repo by discovering your versioning, CI trigger, test gate, and publishing steps, then guiding you through a safe release.

Core Features & Use Cases

Repo-aware release planning: Analyzes your repository and CI to infer release rules and caches them for reuse.
Version selection workflow: Determines current version, calculates patch/minor/major outcomes, validates semver, and asks you to choose.
End-to-end release execution guidance: Provides a pre-release checklist and step-by-step instructions for bumping, tagging, pushing, and verifying.

Quick Start

Run the release assistant as: /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 tagging in a GitHub Actions CI workflow?▼

Semantic versioning and tagging in a GitHub Actions CI workflow can be automated by deriving release rules from your repository sources, validating the version bump, and guiding the commit, tag, and push steps. The release process analyzes your CI trigger to ensure safe distribution.

What is the safest way to publish a patch release with an automated test gate?▼

The safest way to publish a patch release is to use a pre-release checklist that validates your version input, runs the CI test gate, and walks through the bump, commit, tag, and push steps. This ensures the test gate passes before distribution.

How do I calculate the next semver version for patch, minor, or major releases?▼

To calculate the next semver version, the release workflow determines your current version from repository sources and calculates the outcome for patch, minor, or major bumps. It validates the explicit semver input before proceeding with the release.

Does this release guidance work with repositories using common CI systems other than GitHub Actions?▼

Yes, the release guidance applies to repositories with GitHub Actions or other common CI systems. It analyzes your CI trigger and distribution targets to infer the correct release rules for your specific environment.

How do I cache and reuse changelog and versioning rules for future releases?▼

You can cache and reuse versioning rules by loading or building a .omc/RELEASE_RULE.md file. This caches your repo-aware release planning data, including CI triggers and distribution targets, for subsequent release executions.