release

Name: release
Availability: InStock
Author: AsiaOstrich

Guide software releases with semantic versioning and changelog generation.

70|13|Updated Dec 24, 2025

Search Tags:#git #changelog #versioning #npm #release #semver

Ready to run

npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill release-asiaostrich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/AsiaOstrich/universal-dev-standards/tree/main/.gemini/skills/release-standards
Command: npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill release-asiaostrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes and simplifies the complex process of releasing software, ensuring consistency and adherence to best practices for versioning and changelogs.

Core Features & Use Cases

Semantic Versioning: Guides users through MAJOR, MINOR, and PATCH version increments based on changes.
Changelog Management: Assists in generating and updating CHANGELOG.md files according to the Keep a Changelog format.
Release Workflow: Provides a step-by-step process for creating stable, beta, alpha, and RC releases, including Git tagging and publishing.
Use Case: A developer needs to release a new version of their npm package. They can use this Skill to determine the correct version number, update the package.json and CHANGELOG.md, create a Git tag, and prepare for publishing.

Quick Start

Use the release skill to start a new release process for version 1.2.0.

Frequently Asked Questions about release

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

FAQPage Schema

How do I determine the correct semantic versioning increment for my npm package release?▼

To determine the correct semantic versioning increment, you evaluate code changes to increment MAJOR for incompatible API changes, MINOR for backward-compatible features, or PATCH for bug fixes, ensuring consistent package versioning.

What is the best way to generate and format a changelog for a new software release?▼

Generating a changelog is best handled by following the Keep a Changelog format, which standardizes the documentation of modifications, ensuring the CHANGELOG.md file accurately records all version updates and release changes.

How do I manage pre-release versions like beta, alpha, and release candidates?▼

Managing pre-release versions involves applying specific semantic versioning labels for beta, alpha, and release candidate stages, allowing developers to distribute and test early builds before finalizing a stable software release.

Can I automate Git tagging and changelog updates during my release workflow?▼

You can automate Git tagging and changelog updates by following a guided release workflow that integrates semantic versioning rules and standard changelog practices, streamlining the software delivery pipeline.

What are the step-by-step instructions to release an npm package from start to finish?▼

Releasing an npm package step by step involves calculating the semantic version, updating package.json and CHANGELOG.md, creating the corresponding Git tag, and finally preparing the package for publishing.

Why should I standardize my software release process using semantic versioning and Git tags?▼

Standardizing your software release process with semantic versioning and Git tags ensures consistency across builds, provides clear traceability of code changes, and facilitates reliable software delivery pipelines.