ARW Release Manager

Automate build, test, and release workflows for the ARW CLI package.

25|41|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/agenticsorg/hackathon-tv5 --skill arw-release-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ARW Release Manager
Source: https://github.com/agenticsorg/hackathon-tv5/tree/main/.claude/skills/arw-release-manager
Command: npx skills add https://github.com/agenticsorg/hackathon-tv5 --skill arw-release-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and error-prone process of building, testing, and releasing the ARW CLI package across multiple platforms and targets, ensuring consistency and saving developer time.

Core Features & Use Cases

  • Multi-Target Builds: Compiles the CLI for Node.js (napi-rs), standalone executables, and WebAssembly.
  • Release Automation: Manages versioning, testing, documentation updates, and publishing to npm and crates.io.
  • Use Case: When you need to prepare a new version of the ARW CLI for release, this Skill will handle all the necessary build steps, validation checks, and publishing to both npm and crates.io.

Quick Start

Use the ARW Release Manager skill to perform a full release workflow with a dry run.

Frequently Asked Questions about ARW Release Manager

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

FAQPage Schema
What is the best way to publish a napi-rs CLI package to multiple targets?

Publishing a napi-rs CLI package to multiple targets requires coordinating builds for Node.js, standalone binaries, and WebAssembly, followed by validation checks and registry deployment.

Do I need Node.js and Rust installed to run build automation for napi-rs?

Yes, build automation for napi-rs requires Node.js, Rust, Git, and specific build tools to be installed locally to compile binaries, run tests, and publish packages.

Can I perform a dry run before publishing my WASM and standalone binaries?

Yes, you can perform a full release workflow with a dry run to validate build steps, documentation generation, and testing logic before actually publishing to npm and crates.io.

How does version tagging work when releasing a Rust CLI to npm and crates.io?

Version tagging during a Rust CLI release synchronizes version numbers across npm and crates.io registries, applying tags in Git before publishing the compiled napi-rs and WASM targets.