New to Claude Skills? Learn how to install them →

Get Claude Skills
dohooo on GitHub

Helmor CLI

Free

Control Helmor workflows directly from your terminal.

by dohooo1.3k stars on dohooo/helmor
1 views
Updated Jul 24, 2026
Get this skill

Free · Opens the source repo

What Helmor CLI does

The Helmor CLI skill provides a command-line interface for managing and controlling Helmor workflows efficiently. It allows users to perform a variety of tasks directly from the terminal, including inspecting data and settings, managing repositories and workspaces, and sending prompts to agents. This skill is particularly useful for developers and designers who prefer a terminal-first approach to interact with Helmor, enabling them to streamline their workflows without relying on a graphical interface.

With commands like restack, stack, and break, users can easily manage pull request stacks, plan large changes, and split existing changes into manageable parts. This is crucial for teams working on complex projects where maintaining a clean and organized codebase is essential. Additionally, the CLI supports GitHub integration, allowing users to manage their repositories effectively and keep track of changes made during development.

The skill also includes functionality for running Helmor as an MCP server, which facilitates communication between Helmor and other agents or runtimes. This is particularly beneficial for users who need to integrate Helmor into larger systems or workflows. The command reference and help documentation included with the skill ensure that users can quickly find the information they need to execute their tasks efficiently.

Overall, the Helmor CLI skill is designed for users who want to leverage the power of the command line to enhance their productivity and streamline their development processes. Whether you are managing repositories, sending prompts, or inspecting sessions, this skill provides the tools necessary to work effectively with Helmor.

When to use it

Use this skill when you need to perform tasks in Helmor from the terminal, especially for managing complex workflows or repositories.

When not to use it

This skill may not be suitable if you prefer a graphical user interface or are unfamiliar with command-line operations.

What you can build with it

Managing Pull Request Stacks

Use the `stack` command to plan and build a large change as a stack of dependent pull requests.

Inspecting Helmor Data

Run `helmor data` to check the active data directory and database settings.

Running Helmor as an MCP Server

Execute `helmor mcp` to run Helmor as an MCP server, enabling integration with other agents.

How to install Helmor CLI

View source

1. Install with the skills CLI

npx skills add dohooo/helmor/helmor-cli --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by dohooo

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:
helmor cli-status
  1. Check the active data directory and database:
helmor data

Use --json when the output will be parsed by scripts or another tool.

CLI Install And Update

Treat Helmor CLI install/update as beta.

  • Prefer the Helmor desktop onboarding/settings Components panel for installing or repairing the managed CLI entrypoint.
  • Use helmor cli-status to verify whether the PATH entry points at the current app-managed CLI.
  • Do not invent a stable standalone install/update command unless it exists in helmor --help or a subcommand help page.
  • If the user is blocked, ask them to run helmor cli-status and share the output, or inspect the app's Components panel if working inside the Helmor repo.

Helmor Skills Install And Update

Treat Helmor skills install/update as a beta app-managed flow.

  • Prefer the Helmor desktop onboarding/settings Components panel for installing or updating bundled Helmor skills.
  • Do not invent a helmor skills command; the top-level CLI help does not currently expose one.
  • If the user asks to update a bundled Helmor skill inside the repo, edit the skill files directly and validate them with the skill validation tooling.
  • Keep user-facing skill content concise and English-first unless the user explicitly asks for another language.

Common Tasks

Manage Repositories And Workspaces

Use these command groups for local-first project setup and workspace orchestration:

helmor repo --help
helmor workspace --help

When creating workspaces, prefer explicit repo names and concise purpose labels:

helmor workspace new --repo helmor

Inspect Sessions And Files

Use sessions for conversation history and files for editor-surface operations:

helmor session --help
helmor files --help

Send A Prompt To An Agent

Use send when the user wants to dispatch work from the terminal:

helmor send --help

Favor JSON output for automation:

helmor --json send --help

Integrations And Local Tooling

Use the relevant command group:

helmor github --help
helmor scripts --help
helmor models --help

MCP Server

Run Helmor as an MCP server over stdio:

helmor mcp

Use this when another agent/runtime needs to call Helmor through Model Context Protocol.

Command Reference

Read references/helmor-help.md when you need the full top-level helmor --help command list.

For exact flags on a command group, run the group's help instead of guessing:

helmor <command> --help

Frequently asked questions about Helmor CLI

Similar skills

Turborepo

Optimized build system for JavaScript/TypeScript monorepos.

Azure Pipelines Validation

Streamline your Azure DevOps pipeline changes locally.

Azure Developer CLI

Streamline your Azure project workflows with best practices.

Azure Container Registry CLI

Manage Azure Container Registry resources with ease.

Aspire

Build and orchestrate polyglot distributed applications seamlessly.

Vercel CLI

Manage and deploy Vercel projects from the command line.