test-release

Automate end-to-end validation of released Archon binaries across brew, curl-mac, and curl-vps install paths.

23.1k|3.5k|Updated Feb 7, 2025
One-click install
npx skills add https://github.com/coleam00/Archon --skill test-release-coleam00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/coleam00/Archon/tree/main/.claude/skills/test-release
Command: npx skills add https://github.com/coleam00/Archon --skill test-release-coleam00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end validation of released Archon binaries across brew, curl-mac, and curl-vps install paths.

Core Features & Use Cases

  • Automated multi-path release validation: verify binaries across brew, curl install, and VPS install paths.
  • Deterministic phase-driven testing: pre-flight, install, smoke tests, uninstall, and reporting to ensure reproducible results.
  • Built-in artifact verification: records SHA256 and version outputs and provides a structured release report for the team.

Quick Start

Run the test-release skill with a target install path (brew, curl-mac, or curl-vps) to execute automated end-to-end validation of the released Archon binary.

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I automate binary validation for released builds across multiple install paths?

Automated binary validation executes a phased workflow across brew, curl-mac, and curl-vps install paths. It runs pre-flight checks, installs the artifact, executes smoke tests, and uninstalls to ensure deterministic release verification.

What is end-to-end release testing for curl and brew installations?

End-to-end release testing verifies binary integrity by installing artifacts via brew or curl, recording SHA256 hashes, checking version output, and generating a structured release report to ensure reproducible results.

Can I reproduce user bug reports on released binaries using automated smoke tests?

Yes, automated smoke tests validate released binaries to reproduce user bug reports. The workflow installs the specific released build, runs deterministic tests, and records artifact SHA256 and version output for verification.

Does this release testing workflow support VPS environments and curl installs?

Release testing supports VPS environments through the curl-vps install path. It automates artifact installation, executes smoke tests, and uninstalls the binary while recording a structured report for deterministic verification.

How to verify Archon binary integrity after tagging a new version?

Verify binary integrity after tagging by running automated validation across brew and curl paths. The workflow records SHA256 hashes and version outputs, executing smoke tests to generate a structured release report.

What are the limitations of automated phase-driven release testing?

Automated phase-driven testing focuses solely on brew, curl-mac, and curl-vps install paths for Archon binaries. It does not support other package managers or platforms outside its predefined pre-flight, install, smoke test, and uninstall phases.