release

Automate versioned npm package releases with changelog generation and GitHub releases.

947|48|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HazAT/glimpse --skill release-hazat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/HazAT/glimpse/tree/main/.pi/skills/release
Command: npx skills add https://github.com/HazAT/glimpse --skill release-hazat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually cutting software releases involves error-prone, repetitive steps like version bumping, changelog updates, npm publishing, git tagging, and GitHub release creation, which this skill automates to save developer time and reduce human error.

Core Features & Use Cases

  • Automated Changelog Generation: Groups conventional commits into structured, readable changelog sections based on commit prefixes.
  • Interactive Publishing Support: Handles npm authentication and OTP prompts via cmux to streamline the publishing process.
  • End-to-End Workflow Coordination: Manages the full release process from version selection to GitHub release creation with minimal manual input. This skill is ideal for Node.js package maintainers who need to cut reliable, consistent releases without memorizing complex command sequences.

Quick Start

Use the release skill to cut a new patch version of the glimpseui package, publish it to npm, and create a matching GitHub release with auto-generated changelog 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 publishing and GitHub release creation for a Node.js package?

You can automate npm publishing and GitHub release creation by using a tool that coordinates version bumping, git tagging, npm publication, and GitHub release notes into a single interactive workflow. This eliminates manual command sequences and reduces human error.

How does conventional commit based changelog generation work for releases?

Conventional commit based changelog generation works by grouping commit messages into structured, readable sections based on their prefixes. This automatically categorizes features, fixes, and changes without requiring manual changelog edits.

Do I need specific CLI tools to automate git tagging and npm package publication?

Yes, you need the npm and gh CLI tools installed to handle package publication and GitHub release management. You also need cmux for interactive authentication handling during the release process.

What is the best way to handle OTP prompts and npm authentication during an automated release?

The best way to handle OTP prompts and npm authentication is by using cmux to manage interactive inputs. This streamlines the publishing process by automatically handling authentication prompts without manual intervention.

Can I use automated release workflows if my project only has a package.json file?

No, automated release workflows require both a package.json and a CHANGELOG.md file in your project. These files are necessary to update the version number and append the newly generated changelog entries respectively.

Why should I automate version bumping instead of cutting npm releases manually?

You should automate version bumping to eliminate repetitive, error-prone manual steps like changelog updates, git tagging, and npm publishing. Automation ensures consistent, error-free releases and saves significant developer time.