Arashi Skill

Coordinate Git worktrees across configured Arashi workspaces, or use Arashi ad hoc in an unconfigured non-bare Git project.

Start

1. Assume the CLI is installed unless installation was requested or aw --version fails.
2. Use installed aw --help and aw <command> --help as parameter authority.
3. Choose one mode using the section below, and initialize it when the workspace is fresh.
4. After the chosen workspace is initialized or otherwise discoverable, diagnose health with aw doctor --json before lower-level recovery.
5. Load only the reference for the task.

Choose a mode

• Configured mode: Prefer configured mode; use ordinary aw init for shared project settings, groups, workspace or repository hooks, child repositories, or coordinated commands. Explicit in-repo .arashi/config.json fields take priority over the separate optional user file at ~/.arashi/config.json.
• Zero-config standalone mode: use aw init --zero-config only for ad hoc work in an unconfigured non-bare Git project. It does not create or persist workspace .arashi configuration. Personal create/switch/editor and worktree location/naming preferences may use the optional user defaults file in either mode; see Workflows. Passive discovery does not repair ignore coverage, and bootstrap must not edit tracked .gitignore or global Git configuration automatically.

Universal operating rules