release

Automate Node.js releases with version bumps, npm publish, and GitHub notes.

5|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/schemalabz/diavgeia-cli --skill release-schemalabz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/schemalabz/diavgeia-cli/tree/main/.claude/skills/release
Command: npx skills add https://github.com/schemalabz/diavgeia-cli --skill release-schemalabz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual release processes are slow and error-prone, leading to inconsistent versioning and delayed deployments.

Core Features & Use Cases

  • Bump version numbers (patch, minor, major) automatically.
  • Build, publish to npm, tag the release, and draft GitHub release notes.
  • Single-branch workflow with tags applied directly on main to streamline publishing.

Quick Start

Create a new release by bumping the version, building, publishing to npm, tagging, and generating GitHub release notes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm version bumps and GitHub releases?

Automate npm version bumps and GitHub releases by using a workflow that validates git state, bumps package.json versions, builds, publishes to npm, tags the main branch, and generates structured GitHub release notes.

Can I do a dry run before publishing a new version to npm?

Yes, you can perform a dry run before publishing to npm. The release process supports dry-run executions, allowing you to validate the git state and package.json and preview the release steps without pushing tags or publishing.

What is a single-branch workflow for Node.js releases?

A single-branch workflow applies git tags directly on the main branch to streamline publishing. It validates the git state, bumps versions, publishes to npm, and generates release notes without managing separate release branches.

How do I generate GitHub release notes automatically from a git tag?

Generate GitHub release notes automatically by tagging the release on the main branch after an npm publish. The workflow formats the notes using a structured template, capturing the version bump and build output for the GitHub release.

Does the automated release workflow support explicit version ranges?

Yes, the automated release workflow supports explicit-range releases. Alongside standard patch, minor, and major bumps, you can specify an explicit version range to target exact package versions during the build and publish cycle.

Why do my automated npm releases fail due to uncommitted git changes?

Automated npm releases fail when the git state is unclean because the workflow validates the repository before proceeding. It checks package.json and git status to ensure the main branch is stable before bumping versions and tagging.