release

Synchronize version references and publish verified npm and GitHub releases.

20|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill release-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/release
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill release-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk and effort of releasing oh-my-codex by coordinating version updates, testing, tagging, publishing, and release verification in a consistent sequence.

Core Features & Use Cases

  • Version Synchronization: Updates the project version across package metadata, installer code, tests, plugin configuration, and README content.
  • Release Validation: Runs the full test suite before committing and publishing changes.
  • GitHub and npm Publishing: Creates and pushes a version tag, publishes the package to npm, and creates a corresponding GitHub release.
  • Use Case: Use it when preparing a patch, minor, or major oh-my-codex release and you need every version reference and distribution step handled consistently.

Quick Start

Use the release skill to publish the next minor version of oh-my-codex as 2.4.0.

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 npm publishing for a release?

Automate semantic versioning and npm publishing by synchronizing version references, running test validation, committing Git tags, and publishing to npm and GitHub releases in a verified sequence. This ensures every distribution step is handled consistently.

What is the best way to synchronize version bumps across package metadata and documentation?

Synchronizing version bumps across package metadata, installer code, tests, plugin configuration, and README content is handled automatically during the release workflow. This coordinates all version references to ensure consistency before Git tagging and npm publication.

Do I need GitHub CLI authentication and repository write access to automate releases?

Yes, GitHub CLI authentication, repository write access, and npm publishing permissions are required to complete distribution and verification. These permissions allow the release workflow to push version tags, publish packages, and create GitHub releases.

How does test validation work before a Git commit and npm publication?

Test validation runs the full test suite before committing and publishing changes. This release validation step ensures that all tests pass before a Git tag is pushed, the package is published to npm, and the GitHub release is created.

Can I use release automation for patch, minor, and major semantic versioning workflows?

Yes, release automation applies to patch, minor, and major semantic versioning workflows. It coordinates version updates, test validation, Git commits, Git tags, npm publication, and GitHub releases for each semantic version increment type.

Why does my release workflow require npm publishing permissions and GitHub CLI authentication?

Your release workflow requires npm publishing permissions and GitHub CLI authentication to complete distribution and verification across both platforms. Without these, the process cannot push Git tags, publish the package to npm, or create the corresponding GitHub release.