skills.rest
jimmi-joensson
jimmi-joenssonCOMMUNITY
Explore all skills by this author →
GitHub

openwhisper-releases

Automate OpenWhisper releases across Mac and Windows via a draft GitHub Release.

2|Updated Apr 22, 2026
Search Tags:#workflow#github#release#handover#windows#mac#two-machine
One-click install
npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-releases
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openwhisper-releases
Source: https://github.com/jimmi-joensson/OpenWhisper/tree/main/.claude/skills/openwhisper-releases
Command: npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-releases

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenWhisper releases are complex when artifacts must be produced on separate machines and published together. This Skill coordinates the end-to-end release workflow across Mac and Windows hosts, ensuring a single draft GitHub Release acts as the nexus for both halves and the handover process.

Core Features & Use Cases

  • Two-machine release workflow: Split artifact creation between Mac DMG (arm64) and Windows MSI (x64) builds, with consolidated release notes.
  • Versioning & tagging: Bump version numbers in all manifests prior to tagging to keep releases consistent.
  • Handover documentation: Generate or refresh a release-handover doc to guide Windows handoff and post-release tasks.

Quick Start

Start the dual-machine release flow to prepare a vN.M.0 OpenWhisper release across Mac and Windows with a single draft release and a handover document.

Frequently Asked Questions about openwhisper-releases

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

FAQPage Schema
How do I coordinate a release across Mac and Windows machines?▼

Coordinate a dual-machine release by using a single draft GitHub Release as the nexus to split artifact creation, bump versions, and guide the two-artifact handoff between Mac and Windows hosts.

What is a two-machine release workflow for separate build artifacts?▼

A two-machine release workflow splits artifact creation, such as Mac DMG and Windows MSI builds, across separate hosts and consolidates them into one draft GitHub Release with unified release notes.

How do I automate version bumping and tagging for a dual-host release?▼

Automate version bumping and tagging by enforcing a five-step release process that updates version numbers in all manifests prior to tagging to keep multi-host releases consistent.

Do I need a handover document for Windows release handoff?▼

Yes, a handover document is needed to guide the Windows handoff and post-release tasks, ensuring the separate build artifacts are properly coordinated and published together.

Can I use a draft GitHub Release to manage multi-host artifact handoff?▼

Yes, you can use a single draft GitHub Release to manage multi-host artifact handoff, acting as the central nexus for both Mac and Windows builds to ensure coordinated publishing.

What are the limitations of a two-machine release process?▼

The two-machine release process requires separate hosts for specific artifacts, meaning you must maintain consistent versioning across manifests and rely on a manual handover document for the Windows handoff.

Related Skills

Explore More Software Engineering Skills→
vnmoorthyvnmoorthy
2

setup-gbrain

Install and configure the gbrain CLI with local brain initialization and MCP registration.

Community
Intermediate
solo-istsolo-ist
2

release

Automate Prose release packaging, signing, and publishing for MAS and GitHub Releases.

Official
Advanced
spallempatispallempati

ci-build-integrity

Enforce immutable CI builds and generate signed SBOMs for supply chain security.

Community
Advanced
anthrilanthril
3

cicd-pipeline-audit

Audit CI/CD pipeline configs across six platforms for security and deploy-safety risks.

Official
Advanced