dev-release

Automate coordinated GitHub, Homebrew, npm releases for the ralphy CLI.

118|12|Updated May 5, 2026

Search Tags:#automation #git #versioning #cli #release #docs #ci-cd

Ready to run

npx skills add https://github.com/alecs5am/ralphy --skill dev-release-alecs5am

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-release
Source: https://github.com/alecs5am/ralphy/tree/main/.agents/skills/dev-release
Command: npx skills add https://github.com/alecs5am/ralphy --skill dev-release-alecs5am

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Coordinate and automate the release process for the ralphy CLI across GitHub Releases, Homebrew, and npm, eliminating manual handoffs and drift between channels.

Core Features & Use Cases

End-to-end release orchestration across GitHub Release, Homebrew tap, and npm, driven by Conventional-Commits-ish rules.
Automatic changelog drafting, version bump coordination, and public docs sync (docs-mintlify) as part of a single release workflow.
Preflight credential checks, diff baseline tracking, and safe, auditable commit choreography to ensure a clean, reproducible release.

Quick Start

Trigger the release workflow on the main branch when you are ready to publish a new version across all channels.

Frequently Asked Questions about dev-release

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

FAQPage Schema

How do I automate CLI releases across GitHub, Homebrew, and npm?▼

Automate CLI releases across GitHub, Homebrew, and npm by orchestrating end-to-end versioning, changelog drafting, and documentation sync into a single, auditable release workflow. This eliminates manual handoffs and drift between distribution channels.

What is release orchestration for CLI tools and when do I need it?▼

Release orchestration for CLI tools coordinates version bumps, changelog drafting, and multi-channel publishing. You need it when manual handoffs cause drift between GitHub, Homebrew, and npm, or when hotfix patches require coordinated documentation sync.

How do I coordinate versioning and documentation sync for hotfix patches?▼

Coordinate versioning and documentation sync for hotfix patches using Conventional-Commits-ish rules that drive automatic changelog drafting and Mintlify docs planning, ensuring a single, reproducible release baseline across all channels.

Do I need preflight credential checks before triggering a multi-channel release workflow?▼

Yes, preflight credential checks are required before triggering a multi-channel release workflow. They validate access permissions for GitHub, Homebrew, and npm upfront, ensuring safe, auditable commit choreography and preventing mid-release failures.

Does this release orchestration workflow work with Mintlify for public docs?▼

Yes, this release orchestration workflow integrates with Mintlify for public docs. It automatically plans and syncs documentation updates as part of the single release workflow, keeping your public docs aligned with the new version.

What's the best way to ensure a clean, reproducible release baseline across npm and Homebrew?▼

Ensure a clean, reproducible release baseline across npm and Homebrew by tracking diff baselines and applying commit choreography. This approach coordinates versioning and changelog drafting into one auditable workflow on the main branch.