skills.rest
ValorVie
ValorVieCOMMUNITY
Explore all skills by this author →
GitHub

release-standards

Enforce semantic versioning and Keep a Changelog formatting for software releases.

5|1|Updated Jan 14, 2026
Search Tags:#git#changelog#versioning#release#release-management#tagging#semantic-versioning
One-click install
npx skills add https://github.com/ValorVie/custom-skills --skill release-standards-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-standards
Source: https://github.com/ValorVie/custom-skills/tree/main/skills/release-standards
Command: npx skills add https://github.com/ValorVie/custom-skills --skill release-standards-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often struggle with inconsistent release practices, leading to version drift and unclear release notes.

Core Features & Use Cases

  • Semantic Versioning Guidance: Establishes MAJOR.MINOR.PATCH rules, prerelease handling, and build metadata for predictable version bumps.
  • Changelog Formatting: Standardizes changelog entries with sections like Added, Changed, Fixed, and Security.
  • Release Workflows: Documents a repeatable process from version updates to tagging and release notes, including project-specific overrides via CLAUDE.md.
  • Use Case: A team preparing a new release can update version numbers, generate CHANGELOG entries, and publish with correct tags.

Quick Start

Apply these guidelines when preparing a release by updating version numbers and the CHANGELOG according to semantic versioning and Keep a Changelog format.

Frequently Asked Questions about release-standards

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

FAQPage Schema
How do I format a changelog using the Keep a Changelog standard?▼

Changelog formatting standardizes entries into Added, Changed, Fixed, and Security sections. This aligns your release notes with the Keep a Changelog format for consistent documentation across software releases.

When do I need to bump the MAJOR, MINOR, or PATCH version in semantic versioning?▼

Semantic versioning rules require bumping MAJOR for incompatible changes, MINOR for new backward-compatible features, and PATCH for backward-compatible bug fixes. This ensures predictable version bumps during release planning.

What's the best way to automate git tagging and release notes for a new version?▼

Release workflows document a repeatable process from version updates to git tagging and release notes publication. This standardizes release automation by applying semantic versioning and changelog rules across projects.

Can I override default release management rules for a specific project?▼

Yes, project-specific overrides are supported via CLAUDE.md. This allows you to customize versioning, tagging, and changelog workflows while maintaining core semantic versioning standards across other repositories.

How does prerelease handling work in semantic versioning?▼

Semantic versioning guidance establishes prerelease handling and build metadata rules appended to version numbers. This clearly identifies pre-release versions during release planning and prevents version drift.

Related Skills

Explore More Software Engineering Skills→
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate
DonTiziDonTizi
2

release

Automate Python project releases with version bumps, changelog updates, and Git tags.

Community
Advanced
AsiaOstrichAsiaOstrich
70

Release Standards

Guide semantic versioning and changelog formatting for software releases.

Community
Intermediate
edfentonedfenton
3

shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

Community
Advanced