release

Automate version bumping, tests, Git tags, and package publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing new versions of your software, ensuring consistency and saving valuable developer time.

Core Features & Use Cases

  • Automated Version Bumping: Updates version numbers across multiple project files.
  • Testing and Tagging: Executes tests and creates Git tags for new releases.
  • Publishing: Handles publishing to package managers like npm and creating GitHub releases.
  • Use Case: When you're ready to ship a new feature, simply invoke this Skill with the desired version (e.g., 'minor' or '2.5.1') and it will manage the entire release pipeline.

Quick Start

Use the release skill to update the project to the next patch version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publishing and GitHub releases?

You can automate npm publishing and GitHub releases by invoking a release automation skill that bumps versions, runs tests, creates Git tags, and publishes to the npm registry. This end-to-end release pipeline requires only the desired semantic version as input.

How do I bump version numbers across multiple project files for a new release?

Bumping version numbers across multiple project files is handled automatically by the release skill. It updates version strings based on your specified semantic versioning target, such as a patch, minor, or major update.

What is the best way to implement semantic versioning for a patch or minor update?

The best way to implement semantic versioning for patch or minor updates is to use an automated deployment tool. The release skill accepts version keywords like 'minor' or '2.5.1' and manages the entire semantic versioning and tagging process for you.

Does automated version bumping run tests before creating Git tags?

Yes, automated version bumping runs tests before creating Git tags. The release process executes your test suite and only proceeds to create Git tags and publish to package managers if the tests pass.

Can I use this release automation for both npm and GitHub deployments?

Yes, you can use this release automation for both npm and GitHub deployments. It handles publishing to the npm package registry and simultaneously creates corresponding GitHub releases as part of its end-to-end pipeline.

What do I need to start automating my project releases?

To start automating your project releases, you need a project with existing version files and a Git repository. You then invoke the release skill with your desired version increment, and it manages the testing, tagging, and publishing.