release

Analyze repository release rules and cache them in .omc/RELEASE_RULE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release governance for software projects is often manual, error-prone, and hard to scale as teams grow. This Skill analyzes repository release rules, derives a consistent release strategy, and caches results in .omc/RELEASE_RULE.md to speed up future releases.

Core Features & Use Cases

  • Automated rule derivation: Inspects project metadata, CI configurations, and version files to infer release criteria.
  • Local caching: Stores derived rules in .omc/RELEASE_RULE.md to accelerate future releases.
  • Guided release workflow: Provides step-by-step guidance for version bumps, changelog considerations, and tagging/publishing across ecosystems.
  • Use Case: When preparing a release across multiple packages, run the skill to generate a unified plan and cache it for subsequent releases.

Quick Start

Run the release skill to analyze your repository and create or refresh the .omc/RELEASE_RULE.md cache.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git tag creation and semantic versioning for releases?

Automate git tag creation and semantic versioning by analyzing repository metadata and CI configurations to derive release rules. The skill inspects version sources and test gates, caching the strategy to guide automated tagging and publishing.

What is the best way to generate a consistent changelog strategy across multiple packages?

Generating a consistent changelog strategy across multiple packages requires deriving a unified release plan from project metadata. The skill identifies ecosystem-specific changelog considerations and caches them locally to accelerate future releases.

How do I set up CI-CD release rules for first-time repository governance?

Set up CI-CD release rules by running an automated analysis of your repository's version files and trigger configurations. The skill handles first-time setup by deriving rule-driven guidance and caching results for subsequent automated publishing.

Does this release automation tool work without external dependencies?

Yes, release automation works without external dependencies. The skill independently inspects project metadata and CI configurations to identify version sources, test gates, and release triggers across various ecosystems for automated tagging.

Why should I cache derived release rules in my repository?

Caching derived release rules in .omc/RELEASE_RULE.md accelerates future releases by storing previously analyzed version sources and changelog strategies. This local cache eliminates repetitive repository analysis during subsequent guided release workflows.