release

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

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill release-oneforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/oneforce/oh-my-gemini-cli/tree/main/skills/release
Command: npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill release-oneforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow for oh-my-gemini-cli, ensuring consistent version bumps, tests, and publishing across multiple files and artifacts.

Core Features & Use Cases

  • End-to-end release automation: Bumps versions across package.json, installer, gemini plugin files, docs, and readme, runs tests, commits, tags, and pushes, and publishes to npm.
  • Release governance: Generates GitHub releases and maintains version consistency with Semantic Versioning guidelines.
  • Use Case: When preparing a new software release, run the release command to automatically perform all steps from version updates to publishing and release notes creation.

Quick Start

Run a release with /oh-my-gemini-cli:release <version> to automatically update versions, run tests, and publish.

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 version bumping across multiple files?

Automating npm publish and version bumping is handled by synchronizing version updates across package.json, installer, plugin files, and docs, then running tests, tagging, and publishing to npm. This ensures consistent versioning throughout the entire release workflow.

What is the best way to streamline git tagging and GitHub release verification in a CI-CD workflow?

Streamlining git tagging and GitHub release verification involves executing deterministic steps that automatically commit, tag, push, and generate a GitHub release after tests pass. This approach enforces release governance and maintains version consistency across artifacts.

Can I use this release automation to synchronize versions in plugin.json and other config files?

Yes, release automation synchronizes versions across package.json, src/installer/index.ts, .gemini-plugin/plugin.json, docs/GEMINI.md, and readme files. It applies these updates before running tests and publishing to ensure all configuration files match.

How to run an end-to-end release workflow step by step from version update to npm publish?

Running an end-to-end release workflow requires invoking the release command with a target version to automatically update versions, run tests, commit, tag, push, publish to npm, and verify the GitHub release creation in deterministic sequential steps.

Does this release automation support Semantic Versioning guidelines for repository maintenance?

Yes, release automation supports Semantic Versioning guidelines by maintaining version consistency across package.json, plugin files, and release artifacts. It generates GitHub releases that align with semantic versioning requirements during repository maintenance.

Why does version synchronization fail when releasing multiple npm package artifacts together?

Version synchronization fails when release workflows do not apply deterministic steps to update all required files including package.json, installer, and plugin configurations before committing. Automating version bumps across all artifacts prevents manual update errors and misalignment.