skills.rest
marcmunoz-uno
marcmunoz-unoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Coordinate version bumps, tests, tagging, and publishing to npm and GitHub.

3|Updated Apr 2, 2026
Search Tags:#versioning#release automation#continuous testing#npm publish#git tagging#github releases
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill release-marcmunoz-uno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/release
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill release-marcmunoz-uno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and tedium of manual releases by coordinating a consistent, validated version bump, test run, tagging, publishing, and release verification.

Core Features & Use Cases

  • Coordinated version bump across a multi-file project: updates package metadata, installer/version constants, tests, plugin marketplace files, docs markers, and README badges in a single checklist-driven workflow.
  • Validated release readiness with full test execution: enforces running the complete test suite before any git operations or publishing.
  • Automated publishing and release creation: creates and pushes version tags, publishes to npm, and generates a GitHub Release entry for the same version.

Quick Start

Run /oh-my-claudecode:release patch to bump to the next patch version, run all tests, tag the release, publish to npm, and create the matching 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 publish and git tagging in a single workflow?▼

Automated npm publish and git tagging coordinate version bumping, test validation, and publishing to npm and GitHub in one deterministic flow. This removes manual release risk by enforcing test completion before tagging or publishing.

How do I bump version strings across multiple project files during a release?▼

Version bumping updates package.json, installer constants, tests, plugin marketplace metadata, docs markers, and README badges simultaneously. A checklist-driven workflow ensures all versioned files match the provided version input before publishing.

What is the best way to enforce continuous testing before npm publish?▼

Continuous testing before npm publish is enforced by running the complete test suite prior to any git operations. The release process validates full test completion before creating version tags or executing publish commands.

Can I use this release automation for JavaScript and TypeScript projects?▼

Release automation applies to package manager publishing workflows for JavaScript and TypeScript projects. It maintains version strings across multiple project files and handles both npm publishing and GitHub Release creation.

Does automated release creation require explicit version numbers or can I use patch and minor?▼

Automated release creation accepts patch, minor, or explicit version inputs. The provided version input drives all file updates, git tagging, npm publishing, and GitHub Release generation in a deterministic step order.

Related Skills

Explore More Software Engineering Skills→
raphaelchristiraphaelchristi
43

dev:release

Automate npm package releases with changelog generation and GitHub publishing.

Community
Advanced
clawperatorclawperator
2

release-create

Validate version consistency and create annotated git tags for releases.

Official
Advanced
toilahuonggtoilahuongg
10

release

{your code here}

Community
Intermediate
klaudworksklaudworks
181

npm-publisher

Automate npm package releases with version bumps, Git tags, and CI/CD publishing.

Community
Intermediate