skills.rest
cliffthelin
cliffthelinCOMMUNITY
Explore all skills by this author →
GitHub

test-release

Validate installed AXiom Engine/Archon release binaries with smoke tests and SHA-256 reports.

Updated May 13, 2026
Search Tags:#homebrew#regression-testing#sdk-integration#cli-workflows#release-validation#binary-smoke-test#vps-install
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill test-release-cliffthelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/test-release
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill test-release-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A released archon binary can silently fail in real installation contexts, so this Skill verifies the exact artifact works end-to-end after install rather than assuming the build is correct.

Core Features & Use Cases

  • End-to-end release smoke testing across a selected install path (Homebrew on macOS, curl install on macOS, or curl install on a remote Linux VPS).
  • Install integrity and traceability via captured version output and a post-install SHA-256 so bug reports can map to the exact tested artifact.
  • Functional regression checks including version correctness, embedded bundled workflows presence, Claude SDK round-trip (assist), optional env-leak gating, and isolation list sanity.
  • Safety-first operational guardrails that confirm release scope, avoid touching the dev bun link binary, and always clean up/uninstall even when tests fail.

Quick Start

Ask it to run the smoke test on the released artifact by specifying an install path and expected version, for example: "Run /test-release brew 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 verify a released binary works before announcing the update?▼

Run an end-to-end smoke test across real installation paths like Homebrew or curl on a VPS to validate the released binary, capturing version output and SHA-256 for traceability before announcing the update.

How do I reproduce a user-reported bug on a specific released version?▼

Reproduce a user-reported bug by installing the exact released binary via a specified path, running functional regression checks including version correctness and isolation list sanity, and mapping the results to the captured SHA-256 artifact hash.

Does the release validation process support testing curl installs on a remote Linux VPS?▼

Yes, release validation supports testing curl installs on a remote Linux VPS, alongside Homebrew and curl installations on macOS, applying deterministic install-path handling and pre-flight prerequisite checks for each environment.

What is included in a binary smoke test for a new release?▼

A binary smoke test includes pre-flight prerequisite checks, version correctness verification, bundled workflows presence validation, a Claude SDK assist round-trip, optional env-leak gating, and isolation list sanity followed by automatic cleanup.

Why do I need to confirm the install scope before testing a hotfix binary?▼

Confirming the install scope before testing a hotfix binary ensures safety-first operational guardrails are met, preventing accidental modification of the local dev bun link binary and guaranteeing the test targets the re-tagged release artifact.

What happens if the end-to-end smoke test fails during release validation?▼

If the end-to-end smoke test fails during release validation, the structured PASS/FAIL report captures the failure details while the safety-first guardrails automatically execute cleanup and uninstall procedures to restore the environment.

Related Skills

Explore More Software Engineering Skills→
ChatGPT-KBChatGPT-KB

test-release

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

Official
Advanced
Rinzler78Rinzler78
1

bmad-testarch-nfr

Assess non-functional requirements and generate release readiness findings.

Community
Advanced
inbrainfuninbrainfun
174

testing

Validate skill conformance and run daily health checks across the repository.

Community
Advanced
tw-kangtw-kang

shell-runone

Execute a named CUBRID shell testcase locally and report pass/fail results.

Community
Advanced