test-release

Verify released Archon binaries via brew or curl install paths.

Updated May 21, 2026
One-click install
npx skills add https://github.com/sunzcdev/archon-dev-team --skill test-release-sunzcdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/sunzcdev/archon-dev-team/tree/main/.claude/skills/test-release
Command: npx skills add https://github.com/sunzcdev/archon-dev-team --skill test-release-sunzcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that a released Archon binary behaves correctly after installation, so you can confidently confirm the exact artifact users will download (and avoid “works on my machine” release surprises).

Core Features & Use Cases

  • Multi-path install validation: Tests three common install flows—Homebrew (brew), macOS curl installer (curl-mac), and Linux curl installer on a VPS (curl-vps).
  • Artifact certainty: Captures the installed binary path and SHA256 immediately after installation to ensure the test matches the release being reported.
  • Operational smoke suite: Confirms version/build metadata, validates bundled workflow availability, exercises the Claude-based assist workflow (including a resolver error path), optionally checks an env-leak gate, and performs an isolation sanity check.
  • Cleanup and isolation of dev environment: Ensures the developer bun link binary is not touched, and it uninstalls the installed release binary so the system returns to its prior state.

Quick Start

Ask the AI to run the smoke test for the released binary by choosing an install path and (optionally) the version, for example: "Run test-release for curl-mac to verify version 0.3.1."

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I run smoke tests on a released binary before announcing a new version?

Yes, you can validate a Homebrew release installation by installing the binary through brew, capturing its SHA256 and version metadata, and running an operational smoke suite to verify bundled workflows and assist features.

How do I verify a released binary on a remote VPS without affecting my local dev environment?

You verify a released binary on a remote VPS by using the curl-vps installation path to install and test the artifact remotely, ensuring the cleanup process uninstalls it without touching your local bun-linked dev binary.

What does binary smoke testing check during an end-to-end release validation?

To reproduce a release issue, you apply the test-release process against the specific released version by installing it via your chosen path and running the deterministic smoke suite to validate the exact artifact users will download.

Can I test a macOS curl installer for a hotfix release without breaking my existing development setup?

Yes, you can test a macOS curl installer for a hotfix by installing the release binary through curl-mac, running the smoke tests, and relying on the cleanup mechanism to uninstall the binary while preserving your bun-linked dev binary.