Skip to content
Skills Library
Programming · Tool integration

helmor-cli

/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 (`/he

Repository
helmor ↗
Licence
Apache-2.0
Last repository change
24.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/render_stack.py

What it does and when to use it

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 (`/he

Original author description

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 (`/he

How it works

  1. Command Routing
  2. Binary Name (Release vs Dev)
  3. First Checks
  4. CLI Install And Update
  5. Helmor Skills Install And Update
  6. Common Tasks
  7. Command Reference
Original SKILL.md headings · 129 lines, 677 words
SKILL.md preview
---
name: helmor-cli
description: 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`).
---

# 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:

```bash
helmor cli-status
```

2. Check the active data directory and database:

```bash
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:

```bash
helmor repo --help
helmor workspace --help
```

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

```bash
helmor workspace new --repo helmor
```

### Inspect Sessions And Files

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

```bash
helmor session --help
helmor files --help
```

### Send A Prompt To An Agent

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

```bash
helmor send --help
```

Favor JSON output for automation:

```bash
helmor --json send --help
```

### Integrations And Local Tooling

Use the relevant command group:

```bash
helmor github --help
helmor scripts --help
helmor models --help
```

### MCP Server

Run Helmor as an MCP server over stdio:

```bash
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:

```bash
helmor <command> --help
```
Files in this package (8)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • references/break.md 5 KB
  • references/helmor-help.md 2 KB
  • references/restack.md 2 KB
  • references/stack-spec.md 2 KB
  • references/stacked-pr.md 4 KB
  • scripts/render_stack.py 5 KB

Versions

The database has no other skills named helmor-cli.

Database snapshot: 13.11.2026 · package version 2ab92728fb99 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90helmor-debug-loop
    Autonomous local-development debugging loop for Helmor bugs. Use when the user asks an agent to reproduce, diagnose, instrument, fix, or verify a Helmor local dev build issue using repeated local UI simulation, temporary logging, Tauri MCP/towery MCP, screenshots,…
  • 100helmor-debug-operate
    Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility…
  • 100tauri-mcp-cli
    Use the Tauri MCP CLI to start and recover driver sessions, automate Tauri webviews, capture UI state, debug IPC, and work with mobile or remote devices. Use whenever an agent needs to operate a Tauri v2 app from terminal commands.
  • 100github
    Drive GitHub via the official `gh` CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through `gh api`. Use when the user asks to inspect or manage GitHub.
  • 100configure-completions
    Shell completions for a released CLI: generator subcommand, Homebrew/archive/installer delivery, drift test. Use when a repo ships a CLI binary, to add or audit its completions.
  • 100installing-cli-tools
    Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login;…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.