Decide Fit First

• Core job: 将冗长构建日志转化为“阶段定位→根因诊断→修复命令→安全回滚→预防清单”的标准化运维闭环，缩短 MTTR（平均恢复时间）。 | 阶段 | 错误类型 | 关键日志行 | 触发条件 | |:---|:---|:---|:---| | ... | ... | L…
• Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
• Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

• Structure: The skill is organized around “🎯 核心定位”, “🔄 工作流指令”, “📤 输出模板”, “1. 失败定位”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
• Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
• Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

• Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
• Invocation: Name ci-cd-watchdog directly; if the source includes slash commands, start with the command and then add task context.
• Validation: Start small and check whether the result follows “🎯 核心定位 / 🔄 工作流指令 / 📤 输出模板” before expanding.

Boundaries And Review

• Dependencies: It usually needs no extra API key, so start with a small validation task.
• Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
• Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.