Agent skill · software engineering · dohooo
helmor-cli
Use the Helmor CLI to remote-control Helmor from the terminal. Use when the user asks to inspect Helmor data/settings, manage repositories/workspaces/sessions/files, send prompts to agents, list models, use GitHub integration, inspect scripts, run Helmor as an MCP server, generate shell completions, quit a running app, check/install/update the Helmor CLI beta, install/update Helmor skills through the beta app flow, or needs the Helmor command reference. Also plan and build a large change as a stack of dependent PRs (`/helmor-cli stack`), split a change you've already written into a stack (`/helmor-cli break`), and re-sync a stack after lower layers change or merge (`/helmor-cli restack`).
Why this skill is useful
Adds specific commands and workflows for managing Helmor CLI operations that the AI wouldn't reliably generate on its own.
What it needs
Requires helmor installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 1,281 stars on the source repository.
What this skill does
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't re-verify with which / file / --version. If you're a human at a terminal, run <your-worktree>/src-tauri/target/debug/helmor-cli <subcommand> (or whatever path your active Helmor build uses). The rest of every command shape is identical regardless of build. First Checks 1. Check whether the CLI is installed and which data mode it targets: 2. Check the active data directory and database: Use --json when the output will be parsed by scripts or another tool. CLI Install And Update Treat Helmor CLI install/update as beta. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills dohooo/helmor-cli