ops-deploy-fixlisted

Inspect and control the deploy/build auto-fix subsystem. Use for `/ops:deploy-fix status` (last monitor runs, fixer dispatches, locks, hourly budget), `/ops:deploy-fix tail` (follow latest fixer log), `/ops:deploy-fix configure` (re-run the wizard), and `/ops:deploy-fix test` (synthetic dry-run through the pipeline). Trigger when the user mentions deploy auto-fix, post-merge monitor, build fixer, fix budget, fix-agent log, or asks why a deploy didn't get auto-fixed.
Lifecycle-Innovations-Limited/claude-ops · ★ 17 · AI & Automation · score 83

Install: claude install-skill Lifecycle-Innovations-Limited/claude-ops

# /ops:deploy-fix — Auto-fix subsystem control surface 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 | | ------------ | ------------------------------------------------------------------------ | | `status` | Dashboard of recent monitor runs, fixer dispatches, locks, budget | | `tail` | Follow the latest fixer log live | | `configure` | Re-run the wizard from `/o