skills.rest
miethe
mietheCOMMUNITY
Explore all skills by this author →
Website𝕏@MietheGitHub

release

Orchestrate validated software releases across version files, API specs, SDKs, changelogs, and GitHub.

Updated May 3, 2026
Search Tags:#openapi#github release#version bump#sdk generation#git tagging#release orchestration#changelog audit
One-click install
npx skills add https://github.com/miethe/boxbrain-2 --skill release-miethe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/miethe/boxbrain-2/tree/main/.claude/skills/release
Command: npx skills add https://github.com/miethe/boxbrain-2 --skill release-miethe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill coordinates the complex, error-prone process of preparing and publishing a software release while preventing incomplete changelog coverage, stale API artifacts, version mismatches, and premature tagging.

Core Features & Use Cases

  • End-to-End Orchestration: Guides version updates, OpenAPI regeneration, SDK generation, changelog auditing, changelog rollover, commits, tags, and GitHub releases in the required order.
  • Release Safeguards: Enforces audit gates, validates version consistency, preserves OpenAPI-before-SDK sequencing, supports safe dry runs, and requires confirmation for destructive operations.
  • Use Case: Prepare a production release from a clean main branch, identify missing changelog coverage, regenerate derived API artifacts, roll the changelog forward, and publish a correctly tagged GitHub release.

Quick Start

Use the release skill to prepare and validate the next semver release, stopping for confirmation before committing, tagging, or publishing it.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub release orchestration with OpenAPI and SDK generation?▼

To orchestrate a GitHub release, you update version files, regenerate OpenAPI specifications, generate SDKs, audit changelogs, and commit Git tags in a deterministic sequence. This prevents version mismatches and ensures API artifacts are never stale before publishing.

What is the correct sequence for semver release preparation and changelog rollover?▼

Semver release preparation requires updating version files first, followed by OpenAPI and SDK regeneration, changelog auditing, and finally Git tagging. Changelog rollover is idempotent and requires audit-gate enforcement to ensure complete coverage before moving forward.

Can I do a dry run for a production release publication to check changelog coverage?▼

Yes, you can perform a safe dry run to preview a production release publication and audit changelog coverage. The process enforces audit gates and requires human confirmation before executing destructive actions like Git commits, tags, or GitHub releases.

How does SDK generation and git tagging handle OpenAPI-before-SDK sequencing?▼

SDK generation and git tagging preserve OpenAPI-before-SDK sequencing by enforcing deterministic release scripts. This ensures derived API artifacts are regenerated from the updated OpenAPI specification before any SDK generation or Git tagging occurs.

Why does version validation fail during release orchestration if changelog coverage is incomplete?▼

Version validation fails because release orchestration enforces audit gates that check for complete changelog coverage before allowing version bumps. This prevents incomplete changelog rollover and stops premature Git tagging when derived API artifacts are stale.

Related Skills

Explore More Software Engineering Skills→
spartDevspartDev
6

Release Automation

Automate SEMVER version bumps, changelog generation, and release pull requests.

Community
Advanced
jubscodesjubscodes
49

gspdev-publish

Bump version numbers, update changelogs, and prepare npm release artifacts.

Community
Advanced
ExpeditoJExpeditoJ

aiox-devops

Automate GitHub repository management, CI/CD pipelines, and release workflows via scripts.

Community
Intermediate
vericontextvericontext
164

release

Automate VibeFrame version bumps, changelog generation, and commit staging.

Official
Advanced