Hive CLI

Use this skill when the user wants to install Hive, set up Hive in the current project, or inspect, create, advance, review, or administer Hive tasks through the hive CLI.

Before running a Hive workflow, check whether the Hive CLI is installed:

if hive --version 2>/dev/null | grep -qE '^[0-9]+\.[0-9]+\.[0-9]+$'; then
  hive_cmd=hive
elif hv --version 2>/dev/null | grep -qE '^[0-9]+\.[0-9]+\.[0-9]+$'; then
  hive_cmd=hv
else
  hive_cmd=
fi

If hive_cmd is empty, start a guided setup instead of failing. Restate that setup will install the Hive CLI, verify it, install/enable the per-user daemon service, and optionally run hive init for the current project. Get explicit user confirmation before running installers.

Use the host platform to choose one install path:

• macOS arm64: brew tap ivankuznetsov/hive && brew install ivankuznetsov/hive/hive.
• Arch Linux with yay: yay -S --noconfirm --needed hive-bin.
• Arch Linux with paru: paru -S --noconfirm --needed hive-bin.
• Ubuntu 22.04+ / glibc Linux x86_64 or aarch64:

tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
curl -fsSL https://raw.githubusercontent.com/ivankuznetsov/hive/v0.2.0/install.sh -o "$tmpdir/hive-install.sh"
bash "$tmpdir/hive-install.sh"

After install, run the strict hive / hv version check again. If neither command prints a bare X.Y.Z version, stop and report that setup failed or Apache Hive may be shadowing the command. If verification succeeds, run "${hive_cmd}" daemon install once. Then ask whether to initialize the current project; if yes, run "${hive_cmd}" init . --json \x3C/dev/null, followed by "${hive_cmd}" doctor non-fatally. Summarize the installed version, daemon setup result, project initialization result, and any missing runtime dependencies.

Treat /hive setup, /hive install, and /hive bootstrap as requests for the guided setup flow above. Otherwise, treat the user's slash-command text after /hive as arguments for hive_cmd. If no arguments are supplied and Hive is already installed, run "${hive_cmd}" --help and summarize the available workflow. Run commands from the current project/workspace directory unless the user gives another path. Pass arguments safely; do not interpolate raw user text into a shell string.

Prefer --json when the Hive command supports it and you need structured output. Summarize the result, including task slug, stage/action, marker, and next command when present.

Before running destructive admin verbs (drop, uninstall, update, forget, prune, migrate, or metrics), restate the effect and get explicit user confirmation. These verbs can kill agents, remove worktrees, close draft PRs, drop registry entries, or rewrite installed software — they are not undoable.

Before running nested destructive or bypass commands (daemon stop, daemon disable --all, daemon install --force, bot stop, bot install --force, markers clear, or approve --force), restate the effect and get explicit user confirmation. These can stop background automation, replace autostart services, clear recovery markers, or skip terminal-marker safety.

Prefer hive daemon start --detach for daemon startup. Before running hive daemon start without --detach, hive daemon tail, hive bot start --foreground, or hive bot tail, restate that the command can hold the agent in a foreground or streaming process and get explicit user confirmation.