release

Automate version bumps, tests, npm publishing, and GitHub releases.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/INNERJOINT/HarnessSkills --skill release-innerjoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/INNERJOINT/HarnessSkills/tree/main/skills/release
Command: npx skills add https://github.com/INNERJOINT/HarnessSkills --skill release-innerjoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release skill removes manual, error-prone steps in publishing new versions by automating version bumps, test verification, tagging, publishing, and release creation for the repository.

Core Features & Use Cases

  • Version Propagation: Update version values across package.json, source constants, tests, and plugin metadata.
  • Automated Verification: Run the full test suite and require all tests to pass before publishing.
  • Publishing & Releases: Create git tags, push to origin, publish to npm, and create GitHub releases with release notes.
  • Use Case: When preparing a new release, run the skill to reliably bump versions, run tests, tag, publish to npm, and create the GitHub release without manual steps.

Quick Start

Trigger an automated release by running the slash command /oh-my-claudecode:release followed by the version or semantic keyword (for example, /oh-my-claudecode:release 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 npm package publishing and GitHub release creation?

To automate npm package publishing and GitHub release creation, this skill performs version bumps, runs the test suite, creates git tags, publishes to npm, and generates GitHub releases with release notes automatically.

What is the best way to ensure tests pass before publishing an npm package version?

Ensuring tests pass before publishing an npm package version requires an automated release workflow that executes the full test suite and mandates all tests pass before proceeding to the npm publish step.

Can I update the version number across package.json and plugin metadata simultaneously?

Yes, you can update the version number across package.json and plugin metadata simultaneously by running an automated release workflow that ensures consistent version propagation across all relevant project files.

How do I create and push git tags when releasing a new npm package version?

To create and push git tags when releasing a new npm package version, run an automated release command that handles version bumping, executes tests, creates the git tag, and pushes it directly to the origin remote.

Does automated version bumping work with semantic versioning keywords for npm packages?

Yes, automated version bumping works with semantic versioning keywords for npm packages by accepting a semantic keyword input to trigger the release process and update the package version across all project files accordingly.

Why do I need to run a test suite before creating a GitHub release and publishing to npm?

You need to run a test suite before creating a GitHub release and publishing to npm to prevent shipping broken code, as the automated release process mandates successful test execution to verify package stability before public publication.