skills.rest
solitude6060
solitude6060COMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Derive versioning, CI triggers, test gates, and distribution rules from repository inspection.

Updated May 18, 2026
Search Tags:#changelog#versioning#release#git tags#publish#semver#ci workflow
One-click install
npx skills add https://github.com/solitude6060/Yao-skills --skill release-solitude6060
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/solitude6060/Yao-skills/tree/main/skills/release
Command: npx skills add https://github.com/solitude6060/Yao-skills --skill release-solitude6060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releases fail or become inconsistent when teams rely on tribal knowledge for versioning, CI triggers, tests, and changelog conventions.

Core Features & Use Cases

  • Repo-aware release rule discovery: Inspects the repository and CI to determine version sources, release triggers, test gates, distribution/registry targets, and changelog strategy, then caches them in .omc/RELEASE_RULE.md.
  • Incremental refresh with CI drift detection: Detects newer CI/workflow changes since the cached analysis and re-derives only the affected sections.
  • Step-by-step, guided release execution: Computes the target version, produces a pre-release checklist, helps draft release notes, and walks through bump, test, commit, tag, and push steps.

Quick Start

Run a release assistant to analyze your repo and guide the bump, tests, tagging, and push for your next release: /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 changelog generation for my CI workflow?▼

Semantic versioning and changelog generation are automated by deriving release rules from repository inspection, caching them in .omc/RELEASE_RULE.md, and aligning version bumps, changelog strategies, and publish automation with your CI triggers.

What is the safest way to publish a new version to a registry using git tags?▼

A safe publish follows a deterministic release checklist that validates semver inputs, runs test gates, drafts release notes, and walks step-by-step through the bump, commit, tag, and push actions before distribution.

Can I use this release assistant for a multi-package monorepo workflow?▼

Yes, the release assistant targets both typical single-repo and multi-package workflows, deriving version sources, distribution targets, and release triggers specifically for multi-package architectures.

How do I detect CI workflow drift before publishing a new release?▼

CI workflow drift is detected through an incremental refresh mechanism that identifies newer CI changes since the cached analysis and re-derives only the affected release rule sections.

Do I need to manually validate semver inputs before bumping a release version?▼

No, semver input validation is handled automatically as part of the deterministic release checklist, ensuring target version computations are correct before performing any bump, tag, or push actions.

Related Skills

Explore More Product & Management Skills→
jimmi2051jimmi2051

release

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

Community
Advanced
dropsyoondropsyoon

release

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

Community
Advanced
xz1220xz1220

release

Analyze version sources and CI rules to orchestrate repository releases.

Community
Advanced
xdkpxdkp

release

Analyze version sources and CI workflows to derive release rules.

Community
Advanced