rust-cli-binary-rename

Renames a Rust CLI binary across Cargo, release assets, installers, and documentation.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill rust-cli-binary-rename-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-cli-binary-rename
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/rust-cli-binary-rename
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill rust-cli-binary-rename-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Renaming a Rust CLI command is easy to get wrong: changing only the Cargo [[bin]] name breaks updaters, Homebrew formulas, install scripts, and launcher discovery, leaving users with mismatched binaries and broken auto-updates. This Skill coordinates the rename across every surface so the new command works end to end. ## Core Features & Use Cases - Coordinated rename procedure: Step-by-step changes for Cargo [[bin]]/default-run, updater BINARY_NAME constants, release asset naming, install scripts, Homebrew publishing, Windows installer staging, launcher discovery, and clap help text. - Scope guardrails: A decision table for what to keep stable (package name, data home, launcher binary) versus what to rename, plus protection against greedy find-and-replace of tokens like the crate name or repo slug. - Verification checklist: Concrete build, test, and lint commands plus a checklist confirming help output, asset names, and docs are aligned. - Use Case: Grounded in a real rename of the anda CLI to autonogrammer, with a reference file listing every path that had to change and which tokens to protect. ## Quick Start Ask the agent to rename your Rust CLI binary from the old command name to the new one, keeping the package name and data directory unchanged.

Frequently Asked Questions about rust-cli-binary-rename

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

FAQPage Schema
How do I rename a Rust CLI binary without renaming the crate?▼

Change the `[[bin]] name` and `default-run` in Cargo.toml to the new command while leaving the package `name` unchanged. Then update updater BINARY_NAME constants, release asset prefixes, install scripts, and clap help text so every surface emits the new name.

How to rename a CLI binary across Homebrew and GitHub releases?▼

Update the release workflow to copy artifacts as `newname-$target`, set `BINARY_NAME=newname` in install.sh and install.ps1, and adjust the Homebrew publish script's asset URLs and `bin.install` mapping. The formula name can stay old while the installed binary uses the new name.

Why does auto-update break after renaming a Cargo binary?▼

The updater downloads assets by a hardcoded name prefix, so changing only the Cargo bin name makes it fetch old-named assets that no longer exist. The updater's BINARY_NAME constant and the CI release copy step must use the identical new prefix.

What should stay unchanged when renaming a CLI command?▼

Keep the Cargo package name, data home directory (e.g. ~/.anda), secondary launcher binaries, store IDs, and repo slugs stable unless explicitly asked. Use negative lookarounds in bulk replacements so tokens like the crate name or launcher name are not rewritten.

When should I not use this rename procedure?▼

Skip it for TUI-only string rebrands, marketing-site dual branding, or full crate/folder/type renames, which need different workflows. It targets only the user-facing installable command and its distribution surfaces.