skills.rest
az9713
az9713COMMUNITY
Explore all skills by this author →
GitHub

test-release

Smoke-test released Archon binaries across brew, curl-mac, and curl-vps install paths.

Updated Apr 11, 2026
Search Tags:#archon#brew#binary#smoke-test#release-testing#install-paths#curl-install
One-click install
npx skills add https://github.com/az9713/Archon-tutorial --skill test-release-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-release
Source: https://github.com/az9713/Archon-tutorial/tree/main/.claude/skills/test-release
Command: npx skills add https://github.com/az9713/Archon-tutorial --skill test-release-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify a released archon binary works end-to-end via a specific install path.

Core Features & Use Cases

  • Supports three install paths: brew, curl-mac, and curl-vps; installs binaries, runs smoke tests, and cleans up.
  • Validates that the released binary reports the expected version and builds metadata, and verifies binary presence at each install path.
  • Use case: validate a tagged release before publishing, reproduce a user bug from a release, or smoke-test a hotfix binary.

Quick Start

Run this tool to smoke-test a released Archon binary across brew, curl-mac, and curl-vps install paths.

Frequently Asked Questions about test-release

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

FAQPage Schema
How do I automate end-to-end release smoke tests for a binary across multiple install paths?▼

You can automate release smoke tests by validating a released Archon binary across brew, curl-mac, and curl-vps install paths, checking binary presence and verifying expected version and build metadata.

What is the best way to validate a tagged release before publishing it?▼

The best way to validate a tagged release is to run end-to-end smoke tests across brew, curl-mac, and curl-vps install paths to verify binary presence, expected version reporting, and build metadata.

How do I reproduce a user bug from a specific release binary?▼

To reproduce a user bug from a release, apply end-to-end smoke testing to install the specific released binary via brew, curl-mac, or curl-vps paths and verify its workflow behavior and version output.

Do I need scripts/build-binaries.sh and CI artifacts to run release smoke tests?▼

Yes, you need scripts/build-binaries.sh and associated CI artifacts to perform the binary installation, version checks, and basic workflow verification required for comprehensive release smoke testing.

Does this smoke testing approach work with both brew and curl install workflows?▼

Yes, this smoke testing approach supports brew, curl-mac, and curl-vps workflows, installing binaries through each path and verifying binary presence, expected version reporting, and build metadata.

Related Skills

Explore More Software Engineering Skills→
sunzcdevsunzcdev

test-release

Verify released Archon binaries via brew or curl install paths.

Community
Advanced
monomono
5.5k

release-publish

Publish SkiaSharp packages to NuGet.org and finalize releases.

Official
Advanced
fabioc-alohafabioc-aloha

extension-ci-cd

Automate CI/CD pipelines for VS Code extensions with GitHub Actions.

Community
Advanced
ChatGPT-KBChatGPT-KB

test-release

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

Official
Advanced