release

Automate oh-my-gemini releases with version bumps, tests, tags, and publishing.

2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill release-chanhee-kang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/chanhee-kang/oh-my-gemini/tree/main/skills/release
Command: npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill release-chanhee-kang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release workflow for oh-my-gemini, streamlining version bumps, tests, commits, tags, publishing, and release notes to reduce manual overhead and errors.

Core Features & Use Cases

  • Version bump automation: updates version in all locations: package.json, src/installer/index.ts (VERSION constant), src/tests/installer.test.ts (expected version), .claude-plugin/plugin.json, and README.md.
  • Release orchestration: runs tests, commits changes, creates Git tags, pushes to remote, publishes to npm, and creates GitHub releases.
  • Audit-ready: ensures changelog and release notes accompany each release.
  • Use Case: When a maintainer prepares a new version, this Skill runs end-to-end to complete the release with minimal manual steps.

Quick Start

/oh-my-gemini:release <version>

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps across multiple files before an npm release?

Automating version bumps updates the version string across package.json, installer constants, test files, plugin metadata, and README.md simultaneously to enforce consistency before publishing. This eliminates manual file editing and reduces version mismatch errors.

What is the best way to orchestrate a git workflow for releases with tags and GitHub notes?

Release orchestration automates the end-to-end git workflow by running tests, committing changes, creating Git tags, pushing to remote, and generating GitHub releases with notes. This ensures audit-ready artifacts accompany each published version with minimal manual intervention.

Can I execute a one-click release workflow in both local and CI environments?

You can execute the release workflow in both local development and CI environments. The process validates that tests pass, ensures proper tagging, and handles publishing to npm to produce consistent release artifacts regardless of the environment.

How does CI/CD release automation ensure tests pass before publishing?

CI/CD release automation enforces consistency by validating that tests pass before proceeding with version commits, Git tags, and npm publishing. This step prevents broken releases from reaching the registry or creating invalid Git tags.

Do I need to manually update plugin metadata and README files for a new version?

You do not need to manually update plugin metadata or README files for a new version. The automation handles these updates automatically alongside package.json and test constants to ensure all references match the target release version.