release

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

2|1|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/solo-ist/prose --skill release-solo-ist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/solo-ist/prose/tree/main/.claude/skills/release
Command: npx skills add https://github.com/solo-ist/prose --skill release-solo-ist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prose release management is time-consuming and error-prone when done manually; this Skill automates the end-to-end process across Mac App Store and GitHub Releases, reducing manual steps and enabling consistent, signed releases.

Core Features & Use Cases

  • End-to-end release workflow: versioning, building, signing, validating, and publishing artifacts.
  • Multi-channel publishing: Mac App Store and GitHub Releases with automated artifacts and notes.
  • Use Case: A release engineer uses the Skill to prepare a new Prose version by updating version numbers, generating release notes, signing, and publishing to both channels with a single command.

Quick Start

Run /release to start the release workflow, then follow prompts to prepare and publish a new Prose release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate macOS app releases to both the Mac App Store and GitHub?

You can automate macOS app releases by running a single command to handle versioning, building, signing, validating, and publishing artifacts to both the Mac App Store and GitHub Releases.

What is the best way to manage Mac App Store signing identities and provisioning profiles in CI?

Managing Mac App Store signing identities and provisioning profiles in CI is handled by enforcing specific signing configurations during the automated build and release workflow.

How do I prepare a new app version for release with automated packaging and uploading?

To prepare a new app version for release, you initiate the workflow to automatically update version numbers, generate release notes, package the build, and upload the signed artifacts.

Can I publish signed macOS artifacts to multiple distribution channels with one command?

Yes, you can publish signed macOS artifacts to multiple distribution channels with a single command, automating the end-to-end release workflow across the Mac App Store and GitHub.

Does this release automation enforce versioning and CI integration for publish-ready artifacts?

Yes, this release automation enforces strict versioning and CI integration to validate the process and ensure only signed, publish-ready artifacts are delivered to distribution channels.

Why does manual macOS release engineering become time-consuming and error-prone?

Manual macOS release engineering becomes time-consuming and error-prone due to repetitive steps like version updates, signing configurations, and multi-channel uploads that are better suited for end-to-end automation.