release

Compute next versions, generate changelogs, tag, and monitor Codemagic CI builds.

312|38|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/mediar-ai/fazm --skill release-mediar-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mediar-ai/fazm/tree/main/.claude/skills/release
Command: npx skills add https://github.com/mediar-ai/fazm --skill release-mediar-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill automates the Fazm Desktop release process by computing the next version, generating a changelog, tagging with a v*-macos pattern, and monitoring the Codemagic CI workflow to publish the macOS desktop release. It enforces that releases are never built locally.

Core Features & Use Cases

  • Compute next version numbers according to the v*-macos tagging scheme and automatically generate thorough changelog entries.
  • Push a v*-macos tag and monitor the Codemagic CI build that produces and publishes the macOS desktop release.
  • Provide guardrails to ensure releases are performed in CI only, with explicit steps for promotion and validation.

Quick Start

Tag a new release by creating a v*.macos tag and letting Codemagic drive the CI-based build and release process.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate macOS desktop releases via Codemagic CI?

To automate macOS desktop releases via Codemagic CI, use a workflow that computes the next version, generates a changelog, pushes a v*-macos tag, and monitors the CI build to publish the app.

How do I generate a changelog and compute the next version for a release?

Generating a changelog and computing the next version for a release is handled automatically by the workflow, which calculates the new version number based on your v*-macos tagging scheme and compiles thorough changelog entries.

Does the release process allow local builds for macOS desktop apps?

No, local builds are strictly prohibited for macOS desktop releases; the process enforces CI-driven builds with explicit steps for promotion and validation to ensure releases are performed in CI only.

What do I need to set up before starting CI-driven macOS desktop releases?

Before starting CI-driven macOS desktop releases, you need a codemagic.yaml workflow, a v*-macos tag pattern, and associated scripts to verify changelog generation, tagging, and deployment.

Why should I use a v*-macos tag pattern for CI-based versioning?

Using a v*-macos tag pattern for CI-based versioning ensures the automation correctly identifies, tags, and triggers the Codemagic CI workflow to produce and publish the specific macOS desktop release build.

What is the best way to monitor a Codemagic CI build after tagging a release?

The best way to monitor a Codemagic CI build after tagging a release is to use a guided automation workflow that pushes the v*-macos tag and tracks the CI build status through to publication.