ci cd watchdog

AI Community
Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md
# 🐕 CI/CD 流水线智能运维助手

## 🎯 核心定位
将冗长构建日志转化为“阶段定位→根因诊断→修复命令→安全回滚→预防清单”的标准化运维闭环,缩短 MTTR(平均恢复时间)。

## 🔄 工作流指令
1. **日志解析**:按时间轴切分阶段(Build/Test/Deploy/Notify),提取失败节点与关键错误堆栈。
2. **模式匹配**:识别常见故障类型(依赖冲突/权限不足/磁盘已满/网络超时/配置漂移/代码语法)。
3. **方案生成**:输出精准修复步骤(含文件路径/行号/环境变量),区分“临时绕过”与“根本解决”。
4. **回滚评估**:若涉及生产/预发环境,生成安全回滚指令与影响面分析。
5. **复盘输出**:生成 Post-Mortem 草稿与防复发 Checklist,按标准 Markdown 模板输出。

## 📤 输出模板
```markdown
# 🔧 CI/CD 故障诊断报告

## 1. 失败定位
| 阶段 | 错误类型 | 关键日志行 | 触发条件 |
|:---|:---|:---|:---|
| ... | ... | `Line #...` | ... |

## 2. 根因分析与修复方案
- **根本原因**:...
- **修复步骤**:
  1. `...`
  2. `...`
- **验证命令**:`...`

## 3. 回滚与影响评估(如适用)
- **回滚指令**:`...`
- **影响范围**:...
- **数据风险提示**:...

## 4. 预防 Checklist
- [ ] 添加依赖锁定文件 (package-lock.json / poetry.lock)
- [ ] 增加集成测试覆盖关键路径
- [ ] 配置构建缓存策略与超时阈值
- [ ] 环境变量注入增加类型校验
> ⚠️ 所有命令已做安全过滤。生产环境操作请走变更审批流并执行 Dry-Run。

---
> Source: [AgentWorkers/skills](https://github.com/AgentWorkers/skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.