skills.rest
jfriisj
jfriisjCOMMUNITY
Explore all skills by this author →
GitHub

release-procedures

Codify version control, verification, and deployment steps for release readiness.

Updated Aug 23, 2026
Search Tags:#git#workflow#versioning#deployment#release#semver
One-click install
npx skills add https://github.com/jfriisj/real-time-speech-translation-mvp --skill release-procedures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-procedures
Source: https://github.com/jfriisj/real-time-speech-translation-mvp/tree/main/.github/skills/release-procedures
Command: npx skills add https://github.com/jfriisj/real-time-speech-translation-mvp --skill release-procedures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management in software projects is often fragmented, leading to inconsistent version references, missed verification steps, and delayed deployments.

Core Features & Use Cases

  • Versioning governance: Standardize semver usage and ensure version references are consistent across files and docs.
  • Release verification: Define QA/UAT gating criteria to prevent premature releases.
  • Deployment readiness: Provide a repeatable two-stage flow for tagging, publishing, and hand-off to operations.

Quick Start

Use the release-procedures skill to guide the release of version vX.Y.Z for your project.

Frequently Asked Questions about release-procedures

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

FAQPage Schema
How do I standardize semver versioning across my software release workflow?▼

Standardize semver versioning by codifying version control conventions and ensuring version references remain consistent across project files and documentation throughout the release workflow. This prevents fragmented version tracking and inconsistent release identifiers.

What's the best way to add QA and UAT approval gates before a deployment?▼

Add QA and UAT approval gates by defining verification criteria that prevent premature releases, ensuring release readiness is validated before tagging and deployment actions proceed. This gating step blocks unverified commits from entering production.

How do I create a repeatable git tagging and publishing workflow for multiple environments?▼

Create a repeatable workflow by following a two-stage flow for tagging, publishing, and handing off to operations across environments. This codifies deployment readiness steps so each release follows identical verification and publishing actions.

When do I need formal release procedures for my software project?▼

You need formal release procedures when software teams coordinate plan commits, require QA or UAT approvals, and must ensure semver compliance before tagging and publishing. Fragmented release management with inconsistent version references signals the need.

Can I use this release workflow for platform-specific deployment actions?▼

Yes, the release workflow applies platform-specific release actions to ensure deployment readiness across different environments. It defines repeatable steps for tagging and publishing that accommodate platform-specific requirements during hand-off to operations.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced
santosomarsantosomar
1

cd-pipeline-generator

Generate CD pipelines with environment promotion, approval gates, and rollback triggers.

Community
Advanced
jugrajsinghjugrajsingh
1

verifying

Execute test suites and validate acceptance criteria before code integration.

Community
Advanced
wangqianCAIwangqianCAI

openclaw-release-maintainer

Manage OpenClaw release lifecycle with version sync, changelog generation, and artifact validation.

Community
Advanced