release

Name: release
Availability: InStock
Author: vzco

Build, package, sign, and publish ARC Probe releases to GitHub.

15|4|Updated Mar 7, 2026

Search Tags:#automation #github #build #packaging #release #signing #updater

Ready to run

npx skills add https://github.com/vzco/arc-probe --skill release-vzco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/release
Command: npx skills add https://github.com/vzco/arc-probe --skill release-vzco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated, repeatable release management for ARC Probe that automates building, packaging, signing, and publishing new versions to GitHub to ensure consistent deployment artifacts.

Core Features & Use Cases

Build and sign release binaries for all targeted platforms
Assemble release artifacts, update manifests, and generate release notes
Publish releases to GitHub and synchronize plugin/version metadata for downstream consumers Use case: When preparing a new version like 0.2.0, run the release workflow to produce the installer, updater payloads, and notes in a single, auditable process.

Quick Start

Run the release script with the target version to build, package, and publish the new ARC Probe release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate build and release workflows for Windows binaries and installers?▼

Automating build and release workflows for Windows binaries involves coordinating compilation, NSIS packaging, and signing keys within a CI/CD environment. This ensures consistent installer artifacts and updater payloads for each versioned software release.

Can I use GitHub API interactions to publish signed software releases automatically?▼

Yes, you can use GitHub API interactions to publish signed software releases automatically. The workflow coordinates assembling artifacts, applying code signing, and creating the final GitHub release with generated notes.

What is needed to automate packaging and signing in a Windows CI/CD environment?▼

To automate packaging and signing in a Windows CI/CD environment, you need access to code signing keys and NSIS-safe packaging steps. This setup securely builds installers and updater payloads for deployment.

How do I generate release notes and update manifests during a versioned software release?▼

Generating release notes and update manifests during a versioned software release is handled automatically during packaging. The workflow assembles artifacts, synchronizes version metadata, and creates notes for downstream consumers.

Are there limitations when using NSIS packaging steps for automated build and release workflows?▼

Limitations when using NSIS packaging steps include the requirement for a Windows CI/CD environment and access to specific signing keys. The workflow is tailored for targeted platforms and may not apply to non-Windows processes.