omega-loops-cli

Build, install, and smoke-test the Aimee Rust CLI from a local source checkout.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a locally built Rust CLI on PATH after source edits is error-prone: stale debug binaries, dangling symlinks, slow release builds, and smoke tests that accidentally touch real user config. This Skill codifies the canonical debug-symlink install loop and non-interactive smoke suite for the Aimee/Omega CLI workspace. ## Core Features & Use Cases - Debug install loop: Uses scripts/dev-aimee.sh (install, sync, watch, smoke) to symlink target/debug/aimee into ~/.local/bin instead of copying an ~800MB binary with cargo install. - Isolated smoke testing: Runs 15+ clap/porcelain subcommand checks against a temporary AIMEE_CONFIG directory so real credentials and sessions are never touched. - Rebuild automation guidance: Explains why file watchers or a systemd user unit beat cron jobs and non-recursive PathChanged= for keeping the binary current. - Use Case: After renaming crates from omega_* to aimee_*, run the sync command to rebuild incrementally, then verify with aimee --version and the smoke suite before claiming the CLI works. ## Quick Start Ask the agent to run scripts/dev-aimee.sh in the checkout and confirm that aimee --version prints 0.1.0-dev from the symlinked debug binary.

Frequently Asked Questions about omega-loops-cli

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

FAQPage Schema
How do I install a Rust CLI from source without cargo install?▼

Build the debug binary with cargo build -p aimee_main, then symlink it into ~/.local/bin with ln -sfn. The dev-aimee.sh install command automates this, avoiding the ~800MB copy that cargo install --path creates.

How do I smoke-test CLI subcommands non-interactively?▼

Run scripts/dev-aimee.sh smoke, which executes --version, --help, and list/info --porcelain subcommands with a 30s timeout each against an isolated AIMEE_CONFIG temp directory. Interactive commands like provider login or the bare TUI are excluded because they hang.

Why does my CLI still run an old binary after editing the code?▼

The debug binary is not rebuilt automatically after source edits. Run scripts/dev-aimee.sh sync to rebuild only when sources are newer than the binary, or use watch mode with a debounce to rebuild on file changes.

Can I use cron or systemd PathChanged to rebuild a Cargo project?▼

No. Cron jobs with short hard interrupts kill cargo mid-link, and systemd PathChanged= is not recursive so it misses .rs edits under crate directories. Use inotifywait -r with a quiet debounce or the provided watch mode instead.

Why does cargo test fail with 'did not match any packages' after a rename?▼

Crate and binary names may change mid-session, for example omega_* becoming aimee_*. Re-read the [[bin]] name and crates/ directory in Cargo.toml before every verify command instead of assuming a fixed prefix.