test-release

Run automated smoke tests on released Archon binaries across local, macOS, and VPS environments.

Updated May 4, 2026
One-click install
npx skills add https://github.com/BAS-More/Archon --skill test-release-bas-more
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/BAS-More/Archon/tree/main/.claude/skills/test-release
Command: npx skills add https://github.com/BAS-More/Archon --skill test-release-bas-more

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers verify that a newly built or released Archon binary operates correctly end-to-end, reducing the risk of faulty releases reaching users.

Core Features & Use Cases

  • Binary Verification: Runs smoke tests on the Archon binary across different install paths to confirm proper functionality and version correctness.
  • Release Validation: Automates testing the release on local, macOS, and Linux VPS environments to catch issues early.
  • Use Case: When preparing a new release, use this Skill to validate binary integrity, ensure workflows load correctly, and confirm SDK integrations before public distribution.

Quick Start

Invoke the test-release Skill with the target environment and optional version to quickly verify the release's stability and correctness.

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I verify an Archon binary before a release deployment?

To verify an Archon binary before release, you can run automated smoke tests simulating real-world usage scenarios to validate proper functionality and version correctness across different environments.

Can I run binary smoke tests on a Linux VPS and macOS environments?

Yes, binary smoke tests can run on local, macOS, and Linux VPS environments, validating how the Archon binary operates across different install paths to catch deployment issues early.

What is automated release validation for continuous delivery workflows?

Automated release validation for continuous delivery is testing a binary end-to-end through smoke tests to ensure workflows load correctly and SDK integrations function before public distribution.

How do I automate smoke testing to prevent faulty releases from deployment?

You automate smoke testing by invoking validation scripts against the target environment and optional version, running real-world usage scenario simulations to confirm release stability and correctness.

Do I need any specific dependencies to validate binary integrity?

No specific dependencies are required to validate binary integrity, allowing you to execute smoke tests directly on your local system, macOS, or VPS environments without additional setup.

What's the best way to confirm SDK integrations before a public release?

The best way to confirm SDK integrations before a public release is to execute binary verification tests that ensure workflows load correctly and validate end-to-end functionality simulating real-world usage.