claude-code

# Claude Code Router Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this plugin's root directory. Use this skill when the user asks to operate, diagnose, automate, wrap, or explain Claude Code CLI, including `claude`, `claude --print`, `claude plugin`, `claude mcp`, `claude agents`, `claude doctor`, `claude auto-mode`, worktrees, hooks, settings, permissions, custom agents, or ultrareview. For the full command/safety matrix, read `$PLUGIN_ROOT/references/claude-cli-operation-contracts.md`. ## First Move Prefer live local facts over memory. Inspect the installed CLI before building commands or debugging version-sensitive behavior: ```bash python3 "$PLUGIN_ROOT/scripts/claude_code_inspector.py" --json ``` If the user supplies a Claude executable path, use it for the current run: ```bash python3 "$PLUGIN_ROOT/scripts/claude_code_inspector.py" --claude "$CLAUDE_CLI_PATH" --json ``` Do not commit personal absolute paths into source files, manifests, docs, or examples. Use `CLAUDE_CLI`, `PATH`, `ANTHROPIC_API_KEY`, or user-provided runtime arguments instead. ## Routing - Non-interactive `--print`, JSON/stream-json, JSON schema, input streaming, prompt files/stdin, budget caps, fallback model, and no-persistence runs: use `claude-print-automation`. - Plugin marketplac...