release

Orchestrate version bumps, tests, git tags, npm publishing, and GitHub releases.

Updated Mar 17, 2026

Search Tags:#automation #git #release #ci-cd #tagging #version-bump #npm-publish

Ready to run

npx skills add https://github.com/Rheinmir/skills-kit --skill release-rheinmir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Rheinmir/skills-kit/tree/main/skills/release
Command: npx skills add https://github.com/Rheinmir/skills-kit --skill release-rheinmir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end release workflow for the oh-my-claudecode project, removing manual, error-prone steps from the release process.

Core Features & Use Cases

Version bump across multiple locations: package.json, src/installer/index.ts, tests, documentation, and marketplace metadata to ensure consistency.
Full release orchestration: run tests, commit changes, create and push git tags, publish to npm, and create GitHub releases.
Verification & notes: enforce test success before publish and generate release notes for the GitHub release.

Quick Start

Trigger the release workflow with a version to automatically bump versions, run tests, create tags, publish to npm, and generate a 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 version bumps across package.json, tests, and documentation before publishing?▼

Automated release orchestration handles version bumps across package.json, source code, tests, and documentation simultaneously to ensure version consistency. This removes manual, error-prone steps from the process before running tests and publishing.

What is the best way to orchestrate git tagging, npm publishing, and GitHub release creation in one workflow?▼

End-to-end release orchestration coordinates git tag creation, npm publishing, and GitHub release generation within a single automated pipeline. It enforces test success before publish and generates release notes for the GitHub release automatically.

Can I enforce test execution before an npm publish in my CI/CD release pipeline?▼

Yes, automated release workflows enforce test execution before proceeding to npm publish and GitHub release creation. This ensures test success is verified prior to any version tagging or package publishing activities within the pipeline.

Does this release automation workflow work without external dependencies or CI/CD plugins?▼

The release workflow operates without external dependencies, orchestrating version updates, git tagging, npm publishing, and release-note generation internally. It is applicable to software projects requiring a repeatable release pipeline across CI/CD environments.

Why do my manual software releases result in inconsistent versions across project files?▼

Manual release processes often cause inconsistent versions across package.json, source files, and documentation due to human error. Automated release orchestration updates all locations simultaneously, ensuring cross-file version consistency throughout the project.

When should I not use automated release orchestration for my npm package?▼

Automated release orchestration is not suited for projects lacking a repeatable CI/CD pipeline or those requiring highly customized, non-standard publishing flows that cannot be standardized into version bump, test, tag, and publish steps.