release

Automates NPM package releases with version validation, release branches, CI monitoring, and publish verification.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill release-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/packages/ocr-onnx/.agent/skills/release
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill release-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing an NPM package involves many error-prone manual steps: verifying version bumps, checking changelogs, creating release branches, triggering CI workflows, and confirming the publish succeeded. This Skill orchestrates the entire release pipeline so nothing is forgotten or done out of order. ## Core Features & Use Cases - Pre-release validation: Compares the local package version against the published npm version and verifies the CHANGELOG.md contains a matching section before proceeding. - Release branch and CI orchestration: Creates and pushes a release-<package>-<version> branch, triggers the GitHub Actions release workflow, and polls pipeline status until completion. - Publish verification: Confirms the package is live on npm, checks the GitHub release tag, and validates public accessibility by installing the package in a clean environment without authentication. - Use Case: You maintain several packages in a monorepo (e.g., ocr-onnx, tts-onnx). Run /release ocr-onnx to validate, branch, publish, and verify the release end to end, including patch releases from an older release branch. ## Quick Start Release the ocr-onnx package to NPM by running the release workflow with the package name as the argument.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release an NPM package from a monorepo?

Run the release workflow with the package directory name, such as `/release ocr-onnx`. It validates the version bump and changelog, creates a release branch, triggers the CI workflow, and verifies the npm publish and GitHub release.

How do I publish a patch release from an older version branch?

Pass the base branch as the second argument, for example `/release ocr-onnx release-ocr-onnx-0.6.0`. The release branch is created from that base instead of main, letting you ship patches without including newer main changes.

What happens if the version was not bumped before releasing?

The workflow compares the local package.json version against the latest version on npm. If the local version is not higher, the release stops and asks you to bump the version first, preventing duplicate or conflicting publishes.

Why did the release CI pipeline fail?

Common causes are a failing release-merge-guard (missing version bump or changelog section), failing prebuild jobs on a specific platform, or npm publish errors such as an existing version or invalid NPM_TOKEN. Inspect failures with `gh run view <run-id> --log-failed`.

How can I verify an NPM package is publicly accessible after publishing?

Install it in a clean temp directory with an .npmrc pointing only at the public registry and no auth token. A successful install confirms public access; a 401 or 403 error indicates the package may still be private.