test-release

Automate end-to-end smoke testing of released Archon binaries across install paths.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ChatGPT-KB/Archon-mirror --skill test-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/ChatGPT-KB/Archon-mirror/tree/main/.claude/skills/test-release
Command: npx skills add https://github.com/ChatGPT-KB/Archon-mirror --skill test-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the validation of released Archon binaries to ensure end-to-end install paths work correctly and the binary behaves as expected after tagging.

Core Features & Use Cases

  • Automated end-to-end smoke tests across brew, curl-mac, and curl-vps install paths.
  • Verifies key runnable properties: version reporting, basic workflows access, and smoke-test suite execution.
  • Use Case: After a release tag, QA teams run this skill to confirm the binary installs correctly and operates as intended before publishing release notes.

Quick Start

Run the smoke test against the released Archon binary using the chosen install method (brew, curl-mac, or curl-vps) and an optional version target to verify the release.

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I automate smoke testing for released binaries across brew and curl install paths?

Automated smoke testing for released binaries validates end-to-end installation across brew, curl-mac, and curl-vps paths. It executes a phase-driven flow covering pre-flight checks, installation, SHA256 capture, and verification of version reporting and basic operations.

What steps are involved in verifying a binary release through end-to-end smoke tests?

End-to-end smoke tests for a binary release follow a phase-driven flow: running pre-flight checks, executing installation via the chosen method, capturing the SHA256 hash, and verifying version reporting alongside basic workflow operations.

Does this smoke testing approach support both macOS and VPS installation targets?

Yes, the smoke testing approach supports macOS and VPS installation targets by validating release paths across brew, curl-mac, and curl-vps, with optional version verification specifically available for VPS targets.

When do I need to run automated release validation on my binary?

You need automated release validation on your binary immediately after tagging a release. It confirms that the install paths work correctly and the binary behaves as expected before publishing release notes.

Can I verify a specific version target during a VPS smoke test?

Yes, you can verify a specific version target during a VPS smoke test. The testing flow applies to curl-vps paths and includes optional version target verification to ensure the correct release is validated.

What runnable properties are checked during an automated binary smoke test?

An automated binary smoke test checks key runnable properties including version reporting, access to basic workflows, and execution of the smoke-test suite to confirm the released binary operates as intended.