helmor-cli

# Helmor CLI Use this skill to guide simple terminal-first Helmor workflows. Keep the answer practical: prefer one or two concrete commands over a long CLI tutorial. ## Command Routing Route by the first word after `/helmor-cli`: - `restack` — re-sync a PR stack after a lower layer changed or merged. Follow `references/restack.md`. (This is what the composer's **Restack** button sends.) - `stack` — plan and build a large change as a stack of dependent PRs. Follow `references/stacked-pr.md`. - `break` — split the change you've ALREADY written in the current workspace into a stack of smaller dependent PRs, confirming the slicing granularity with the user first. Follow `references/break.md`. - Anything else (or no argument) — an ordinary Helmor CLI task; use the binary-name guidance and command reference below. ## Binary Name (Release vs Dev) Examples below use the literal name `helmor` — the binary a release user has on their PATH. - **Release builds**: invoke commands as `helmor <subcommand>`. - **Dev builds**: do NOT assume `helmor-dev` is on PATH. Under Helmor's worktree-based dev workflow every worktree has its own `target/debug/helmor-cli`, and a shared `/usr/local/bin/helmor-dev` symlink (if it exists) can only point at one of them. Instead: - If you're an **agent running inside Helmor**, the system prompt has already handed you the exact CLI invocation to use (typically an absolute path like `<worktree>/src-tauri/target/debug/helmor-cli`). Call it verbatim — don...