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

• Filter before broad mutation. For mutating, expensive, network-heavy, or long-running multi-repository commands, use --group or --only unless the user explicitly requested every managed repository.
• Preserve existing Git state. Preview broad removal with aw remove --dry-run; do not delete worktrees, branches, or uncommitted changes without explicit scope.
• Never create or modify global Git ignore configuration for Arashi. In configured workspaces, choose repository-local, tracked, or no-write ignore policy deliberately; bare repositories report administrative paths without editing ignore files.
• Use --json for parsed non-interactive output. Treat JSON_UNSUPPORTED_FOR_MODE as a structured refusal for interactive, shell-code, or launch behavior.
• Treat launcher and hook failures as real failures. Do not synthesize terminal/session identifiers, bypass user security policy, interpolate user paths into shell source, or silently fall back to a different launcher.
• Prefer linked references over repeating command-specific rules here.

Task routing

• Install, update, or shell completion: Setup commands and Prerequisites
• Initialize, add, clone, configure an existing workspace, or repair managed paths: Workspace commands
• Run across repositories, parse JSON, hand off, or push: Automation commands
• Create coordinated worktrees or move changes: Create commands
• Switch, launch, or select a session context: Switch and launch and Session shortcuts
• Finish a coordinated workspace, remove, or prune: Finish, remove, and maintenance and Hooks
• Choose an end-to-end goal: Workflows or the Tutorial
• Diagnose a failure or operational security boundary: Troubleshooting and Prerequisites

References

• Command family index
• Workflows
• Hooks
• Session shortcuts
• Tutorial
• Troubleshooting
• Cheat sheet

Current installation and product documentation: https://arashi.haphazard.dev. Compact upstream context: https://arashi.haphazard.dev/llms.txt.