菜单
Investigate a failed deployment in an isolated, read-only subagent. Use when the deploy-watch monitor reports "Deploy FAILED", or when the user asks why a deploy failed and wants the investigation off the main context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | investigate-deploy |
| description | Investigate a failed deployment in an isolated, read-only subagent. Use when the deploy-watch monitor reports "Deploy FAILED", or when the user asks why a deploy failed and wants the investigation off the main context. |
| context | fork |
| agent | claude-code-monitor-examples:deploy-investigator |
Investigate the deployment failure described here: $ARGUMENTS
Follow your investigation procedure and report evidence-backed findings.
Start (or mark the start of) an application deploy and begin live status tracking. Invoke this whenever a deployment is kicked off so the deploy-watch monitor begins signaling in the background when the deploy completes or fails. Use for "deploy the app", "ship it", "watch this deploy"; prefer deploy-watch-setup first when a project uses internal/custom deploy commands or package scripts that provider auto-detect cannot classify exactly.
Creates a project-scoped deploy-status check for the deploy-watch monitor, tailored to a project's own package scripts, internal commands, deployment wrappers, or custom deploy tooling. Use when setting up or configuring deploy tracking for a project, when provider auto-detect (GitHub Actions, Fly, Vercel) cannot read the deploy stack, or when the user says "set up deploy watching", "scope deploy-watch", or "make deploy-watch work with my deploy".
