mcpbeat

Automating Devops

telagod/automating-devops

DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image publishing, testing, monitoring, or infrastructure automation.

15k tokens
context cost
the whole folder, loaded on every use
9
files
instructions only
0
copies elsewhere
how many repositories repackaged it
238
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/telagod/code-abyss --skill automating-devops

The instruction itself

2 sections, as written by the author

炼器秘典 · DevOps

> 判断先于执行:决定「是否做 / 选什么 / 如何取舍」(栈、方案、架构、权衡)前,先读领域判断内核 skills/_kernel/backend/SKILL.md——它管 judgment,本秘典管 execution;冲突时以内核判断为准。

路由

| 意图 | 秘典 | 核心 |

|------|------|------|

| 版本控制 | git-workflow | Git 分支策略、PR 流程、rebase vs merge |

| 测试 | testing | 单元/集成/E2E、TDD、覆盖率 |

| 安全开发 | devsecops | CI/CD 安全、SAST/DAST、供应链 |

| Release 编排 | release-pipelines | release.yml 多 job 骨架、metadata tag、cosign 集成、踩坑字典 |

| 数据库 | database | SQL/NoSQL 选型、索引优化、迁移 |

| 性能 | performance | Profiling、火焰图、基准/负载测试 |

| 可观测 | observability | 日志/指标/追踪三支柱、SLO/SLI |

| 成本 | cost-optimization | FinOps、右尺寸、Spot、自动伸缩 |

CI/CD 管道模式

| 阶段 | 动作 | 工具示例 |

|------|------|----------|

| Commit | lint + unit test + SAST | ESLint、pytest、Semgrep |

| Build | 构建 + 镜像打包 | Docker、Buildpacks |

| Test | 集成测试 + E2E | Playwright、k6 |

| Security | DAST + 依赖扫描 + 密钥检测 | OWASP ZAP、Trivy、gitleaks |

| Deploy | 渐进发布(canary/blue-green) | ArgoCD Rollouts、Flagger |

| Verify | 冒烟测试 + SLO 校验 | Prometheus、Grafana |

| Rollback | 自动回滚(SLO 违约) | ArgoCD、Helm rollback |

原则

自动化一切 | 快速反馈(<10min) | 主干开发短分支 | 不可变制品 | 环境即代码

How to use it

Copy the folder

Take telagod/automating-devops from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.