Verified:GitHub

release

Automates oh-my-claudecode release workflow with npm publish and GitHub tagging.

Updated Feb 20, 2026

Search Tags:#semantic versioning #release automation #tagging #GitHub releases #version bump #npm publishing #CI testing

Ready to run

npx skills add https://github.com/ssccio/cc-on-web-base --skill release-ssccio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/release
Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill release-ssccio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of preparing, testing, tagging, and publishing an oh-my-claudecode release across multiple files and platforms.

Core Features & Use Cases

Version-wide updates: Updates release version values in package metadata, installer code, plugin manifest, and README to keep everything consistent.
Release readiness validation: Runs the full test suite and enforces that all tests pass before publishing.
End-to-end publishing: Creates a commit for the version bump, tags the release, pushes to GitHub, publishes to npm, and generates the GitHub Release entry.

Quick Start

Run /oh-my-claudecode:release patch to bump the patch version, execute the full test run, tag the release, publish to npm, and create the corresponding GitHub Release.

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 release creation for a version bump?▼

Automating npm publishing and GitHub release creation requires coordinating version bumps across package files, running tests, tagging commits, and pushing artifacts. This workflow executes those steps end-to-end, ensuring package metadata, installer code, and manifests stay consistent before publishing.

What is semantic versioning release automation for npm packages?▼

Semantic versioning release automation programmatically updates version numbers in project files, validates the codebase via test suites, and distributes the package. It applies patch, minor, or major version increments while maintaining consistent version tags across repositories and npm registries.

How do I update version numbers across package.json, README, and installer code before publishing?▼

Updating version numbers across package.json, README, and installer code is handled automatically during the release workflow. The process modifies all required version files simultaneously to ensure repository metadata remains consistent before executing npm test:run and publishing artifacts.

Can I publish to npm if my CI testing fails during the release workflow?▼

Publishing to npm requires the full test suite to pass during the release workflow. Release readiness validation enforces that npm test:run completes successfully before version tagging, npm publishing, and GitHub release creation are permitted to execute.

What's the best way to tag and push a release commit to GitHub for npm packages?▼

Tagging and pushing a release commit to GitHub is best handled by automating the entire sequence from version bump to publication. This approach creates a commit for the version bump, generates a consistent v<version> tag, pushes to GitHub, and creates the corresponding GitHub Release entry.

Does this release automation workflow support patch, minor, and major semantic version increments?▼

The release automation workflow supports patch, minor, and major semantic version increments. You specify the increment level when initiating the command, and the process applies that version bump across all repository metadata, tags, and downstream distribution channels.