afm-build-promote-nightly

Build AFM stable releases from main HEAD or nightly commits with validated patches and packaging.

324|17|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/scouzi1966/maclocal-api --skill afm-build-promote-nightly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: afm-build-promote-nightly
Source: https://github.com/scouzi1966/maclocal-api/tree/main/.claude/skills/afm-build-promote-nightly
Command: npx skills add https://github.com/scouzi1966/maclocal-api --skill afm-build-promote-nightly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the complex, multi-step process of promoting AFM from development to a stable release, ensuring patch integrity, version consistency, and safe publishing across Homebrew and PyPI.

Core Features & Use Cases

  • End-to-end release orchestration: from source selection to final GitHub release.
  • Automated validation & patch verification: ensures patches are applied and tested.
  • Dual-channel packaging: builds and packages for Homebrew and PyPI, with staging validation.
  • Auditable provenance: keeps a rollback state snapshot and tag history for traceability.

Quick Start

Initiate the stable release workflow by selecting the source (main HEAD, nightly, or a specific commit) and specifying the target version.

Frequently Asked Questions about afm-build-promote-nightly

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

FAQPage Schema
How do I automate a stable release for Homebrew and PyPI from a nightly build?

To automate a stable release, you select a source like main HEAD or a nightly commit, validate patches and versions, package artifacts for Homebrew and PyPI, run staging tests, and publish the GitHub release across production taps.

What is the safest way to promote a development build to a stable release?

Safely promoting a stable release involves enforcing gated checks and staging tests, verifying patch integrity, ensuring version consistency, and maintaining auditable provenance with rollback state snapshots before final publishing.

Can I build a stable release from a specific commit instead of the main branch?

Yes, you can build a stable release by selecting the source as main HEAD, a nightly build, or a specific commit, followed by applying patches and validating artifact packaging before release.

How do I verify patch integrity and version consistency before publishing to PyPI?

Patch integrity and version consistency are verified through automated validation checks during the build process, ensuring patches are applied correctly and version files are structured properly before staging tests.

What steps are needed to package a web UI and publish a GitHub release to staging taps?

Packaging and publishing requires building the web UI, validating artifacts, updating version files and READMEs, running gated staging tests, and publishing the release to staging taps before promoting to production.

Do I need to run staging tests before publishing a release to production Homebrew taps?

Yes, staging tests are required as gated checks before publishing to production Homebrew taps, ensuring artifact verification and version consistency pass before the final release.