brikko-studio-release-maintainer

Automate Brikko Studio release management from branch cutting to publishing.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill brikko-studio-release-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brikko-studio-release-maintainer
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill brikko-studio-release-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manual Brikko Studio release management is tedious and error-prone, requiring precise version syncing across dozens of project files, changelog generation, cross-platform validation, and coordinated publishing to npm and macOS, with strict compliance guardrails to avoid breaking user updates.

Core Features & Use Cases

  • End-to-end release orchestration: Automates release branch cutting from main, version syncing across package.json, mobile app plists, and documentation, changelog rewriting from commit history, and pre-publish validation.
  • Multi-platform publish coordination: Manages npm package publication, macOS app signing/notarization, Sparkle update feed updates, and beta/stable channel tagging with proper dist-tag management.
  • Release communication automation: Generates full changelog-backed GitHub release notes and formatted public release tweets aligned with Brikko Studio's brand voice. Use case: A Brikko Studio maintainer preparing a new stable release can use this skill to automate the entire workflow from cutting the release branch to publishing artifacts and announcing the release, reducing human error and ensuring all compliance and quality guardrails are met.

Quick Start

Use this skill to request the AI prepare and publish the next Brikko Studio stable or beta release, including version syncing, changelog generation, pre-publish validation, and public release communications.

Frequently Asked Questions about brikko-studio-release-maintainer

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

FAQPage Schema
How do I automate npm publish and macOS signing for a desktop app release?

Automate npm publish and macOS signing by orchestrating end-to-end release workflows that manage npm dist-tag promotion alongside macOS app signing, notarization, and Sparkle feed updates to eliminate manual cross-platform errors.

What is the best way to generate changelogs from commit history for beta releases?

Generate changelogs from commit history by automatically rewriting commits into structured release notes during the release branch cutting process, ensuring accurate version syncing across package files and documentation for both beta and stable channels.

How does pre-publish validation work for npm packages and macOS app updates?

Pre-publish validation works by enforcing release guardrails and coordinating cross-platform validation suites before publication, checking version syncing and compliance to prevent breaking user updates via npm or Sparkle feeds.

Can I use this release management workflow for both stable and beta channel tagging?

Yes, you can use this workflow for stable and beta channel tagging. It manages npm dist-tag promotion and coordinates publication across channels, cutting release branches from main to prepare either release type.

Do I need to manually sync versions across package.json and documentation before publishing?

No, you do not need to manually sync versions. The release automation handles version syncing across package.json, mobile app plists, and documentation automatically as part of the release branch preparation.

Why does release management require strict compliance guardrails for desktop applications?

Release management requires strict compliance guardrails to avoid breaking user updates. Enforcing these checks during pre-publish validation and authentication flows for macOS notarization ensures safe, coordinated artifact distribution.