Release Standards

Guide semantic versioning and changelog formatting for software releases.

70|13|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill release-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Standards
Source: https://github.com/AsiaOstrich/universal-dev-standards/tree/main/locales/zh-CN/skills/release-standards
Command: npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill release-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides you through the complexities of software releases, ensuring consistency, clarity, and adherence to industry best practices for versioning and changelogs.

Core Features & Use Cases

  • Semantic Versioning: Enforces MAJOR.MINOR.PATCH versioning rules for predictable releases.
  • Changelog Generation: Assists in creating and maintaining clear, informative changelogs following the Keep a Changelog format.
  • Release Workflow: Provides a step-by-step process for preparing, executing, and verifying software releases.
  • Use Case: When preparing to release a new version of your npm package, use this Skill to determine the correct version bump, update your CHANGELOG.md, and generate the Git tag.

Quick Start

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

Frequently Asked Questions about Release Standards

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

FAQPage Schema
How do I determine the correct semantic versioning bump for my software release?

Semantic versioning requires a MAJOR bump for incompatible API changes, a MINOR bump for backward-compatible features, and a PATCH bump for backward-compatible bug fixes to ensure predictable software releases.

What is the best way to format a changelog for a new release?

Changelog formatting follows the Keep a Changelog standards, organizing release entries into Added, Changed, Deprecated, Removed, Fixed, and Security categories to maintain clear and informative version histories.

How do I handle pre-release identifiers like alpha and beta in my versioning workflow?

Pre-release identifiers like alpha, beta, and rc are appended to semantic versions using a hyphen, allowing you to denote unstable iterations and test builds before executing a final stable Git tag release.

What is the standard Git workflow for executing a software release?

The standard Git release workflow involves determining the correct version bump, updating the changelog, committing the changes, and generating a Git tag to mark the specific release point in the repository history.

Can I use this release workflow for an npm package?

Yes, the release workflow supports npm packages by guiding you through semantic versioning rules, changelog updates, and Git tagging to prepare and execute consistent versioned package releases.

When should I avoid using semantic versioning for my project?

Semantic versioning is not suitable for projects lacking a public API or those with continuous deployment models that do not require distinct versioned release milestones, as it relies on tracking explicit feature and fix increments.