ops-deploy-fix

# /ops:deploy-fix — Auto-fix subsystem control surface Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). This skill is the operator console for the post-merge + build-failure auto-fix loop installed by `/ops:setup` Step 6.5a. The underlying daemons, hooks, and prompts live in `${CLAUDE_PLUGIN_ROOT}/scripts/`, `${CLAUDE_PLUGIN_ROOT}/hooks/`, and `${CLAUDE_PLUGIN_ROOT}/prompts/`. State lives in `~/.claude/state/ops-deploy-fix/`. Logs live in `~/.claude/logs/ops-deploy-fix/`. **Plugin rules apply (see `claude-ops/CLAUDE.md`).** In particular: - Rule 0 — never echo personal data (slugs are fine, but redact tokens, webhooks, emails) - Rule 1 — max 4 options per `AskUserQuestion` - Rule 4 — background by default during `configure` - Rule 5 — destructive ops (clearing locks, wiping state) require explicit per-action confirmation - Rule 6 — this skill never sends outbound comms; if a future flow needs to, use the universal send gate ## Arguments The first positional argument selects the subcommand. If absent, present: ``` /ops:deploy-fix — what do you want to do? [status] [tail] [configure] [test] ``` Subcommands: | Subcommand | Purpose | | ----------- | ------------------------------------------------...