release

Automate version bumps, tests, tagging, and npm publishing for oh-my-claudecode releases.

16|3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sehoon787/my-claude --skill release-sehoon787
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/sehoon787/my-claude/tree/main/skills/omc/release
Command: npx skills add https://github.com/sehoon787/my-claude --skill release-sehoon787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release workflow for oh-my-claudecode, reducing manual coordination and human error in versioning, testing, tagging, and publishing release artifacts.

Core Features & Use Cases

  • Automates version bumps across multiple files and artifacts to keep releases in sync.
  • Enforces test execution and validation before publishing, ensuring release quality.
  • Handles Git tagging, GitHub releases, and marketplace/plugin metadata updates to produce a complete release.

Quick Start

Run the release command with the target version to start the automated release workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm version bumps and publishing across multiple project files?

Automating npm release workflows coordinates version increments across multiple files, runs validation tests, and handles Git tagging. This synchronizes release artifacts and produces a consistent, auditable publishing process.

What is an automated release workflow for git and npm?

An automated git and npm release workflow orchestrates version increments, test execution, and publishing steps. It enforces file updates and test validation to ensure consistent release quality across project components.

How do I enforce test execution before publishing a release to npm?

Enforcing test execution before npm publishing requires the release workflow to run validation checks and update files prior to publishing. This blocks the publish step until tests pass, ensuring release quality.

Does this release automation handle GitHub releases and Git tagging?

Yes, release automation handles Git tagging, GitHub releases, and plugin metadata updates. It produces a complete release by coordinating these steps alongside version bumps and npm publishing.

Can I use this workflow to keep version numbers in sync across project components?

Yes, this workflow keeps version numbers in sync across project components by automating version bumps across multiple files and artifacts. This ensures all project parts share a consistent release version.

What are the limitations of automating version bumps and tagging in a multi-step release?

Automating multi-step releases requires strict sequencing: updating multiple files, running tests, and producing artifacts before publishing. This enforced coordination ensures auditability but may slow down rapid patch deployments.