test-release

Validate released archon binaries across multiple install environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive automated testing framework to validate a released archon binary's functionality and stability.

Core Features & Use Cases

  • End-to-End Release Verification: Runs smoke tests on installer paths like Homebrew, curl on macOS, and SSH on VPS, ensuring the binary performs as expected.
  • Version & SHA Validation: Checks the binary's version and integrity to ensure the correct build is tested.
  • Use Case: When preparing a new release, QA teams can employ this Skill to confirm release quality and prevent faulty deployments.

Quick Start

Input the target environment and optional version to initiate automated release validation and receive a detailed report on test outcomes and potential issues.

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I automate release validation for a binary across multiple environments?

Automated release validation runs smoke tests on installer paths like Homebrew, curl, and SSH to verify binary functionality. It checks version correctness, SHA integrity, and operational stability across diverse install scenarios to ensure release quality.

Can I use automated QA testing to gate my continuous integration releases?

Automated QA testing is suitable for continuous integration and release gating. By validating a released binary across multiple environments, it confirms version correctness and operational functionality, preventing faulty deployments from proceeding through the pipeline.

What is the best way to verify binary integrity and version correctness before a release?

Verifying binary integrity and version correctness involves checking the SHA and version output of the released binary. This automated validation ensures the correct build is tested and performs as expected before finalizing the deployment.

Does this release testing framework support smoke tests for both macOS and VPS install paths?

Release testing supports smoke tests for macOS installer paths like Homebrew and curl, as well as SSH on VPS. It automates thorough validation of the released binary across these diverse environments to ensure operational functionality.

How do I initiate automated release testing for a specific target environment?

To initiate automated release testing, input the target environment and an optional version. The validation process runs automatically and generates a detailed report on test outcomes and potential issues across the specified install scenario.