AGENT SKILL

haiku-setup

Configure H·AI·K·U for this project — auto-detect VCS, hosting, CI/CD, and providers

01 前言 Front Matter

name: haiku-setup
description: Configure H·AI·K·U for this project — auto-detect VCS, hosting, CI/CD, and providers

Configure .haiku/settings.yml by auto-detecting the environment and confirming with the user.

Detect: VCS (git/jj), hosting (remote URL), CI/CD (workflow files), default branch.
Providers: Use ToolSearch to discover available MCP providers for ticketing, spec, design, comms.
Confirm: Present detected settings via ask_user_visual_question. Allow adjustments.
Configure providers: For each confirmed provider, collect required config from $CLAUDE_PLUGIN_ROOT/schemas/providers/{type}.schema.json.
Workflow tuning: Ask about mode, granularity, default studio, review agents, etc.
Write: Save .haiku/settings.yml preserving existing fields. Commit.
Done: Display summary. Suggest /haiku:haiku-start.

Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding

Show the running H·AI·K·U MCP binary version, plugin version, and whether the engine is the dev source build or the compiled bundle

Unarchive an intent — restore a previously archived intent to default lists

Poll configured providers for events that should create intents or advance gates

Browse available H·AI·K·U studios grouped by category with help links into each studio definition

Install, remove, or preview the H·AI·K·U custom Claude Code status line — a one-line stage/phase indicator for the active intent