release

Automate the seven-step release workflow for oh-my-claudecode.

38.5k|3.5k|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill release-yeachan-heo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/release
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill release-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end release workflow for oh-my-claudecode, reducing manual overhead and ensuring consistent versioning and publishing across all required artifacts.

Core Features & Use Cases

  • Version bumping: Update version numbers consistently across package.json, installer, tests, and plugin files.
  • Release automation: Run tests, commit changes, create and push tags, publish to npm, and create GitHub releases.
  • Use Case: When releasing a new version, trigger the skill with the target version to perform all necessary steps in a repeatable sequence.

Quick Start

Use the release skill to publish a new version, e.g., /oh-my-claudecode:release 2.5.0, or /oh-my-claudecode:release minor.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publish and git tagging for a new version release?▼

You can automate npm publishing and git tagging by triggering a deterministic seven-step workflow that bumps versions, runs tests, commits, tags, and publishes to npm with a single command.

What is the best way to bump version numbers consistently across package.json and installer files?▼

Bumping version numbers consistently across package.json, installer scripts, README, and plugin files requires a coordinated release workflow that updates all artifacts simultaneously to prevent version mismatch.

Can I release a minor version automatically without manually editing package.json?▼

Yes, you can release a minor version automatically by triggering the skill with a minor keyword, which initiates the version bump across all required files without manual editing.

Does this release automation workflow support GitHub release creation alongside npm publishing?▼

Yes, the release automation workflow supports GitHub release creation alongside npm publishing, handling both operations sequentially within its seven-step process after tests pass.

What happens if tests fail during the automated version release process?▼

If tests fail during the automated version release process, the deterministic workflow halts before committing or tagging, preventing broken code from being published to npm or pushed as a git tag.

Do I need any external dependencies to run this CI CD release workflow?▼

No external dependencies are required to run this CI CD release workflow, as it operates as a self-contained skill managing version bumps, tests, commits, tags, and npm publishing independently.