mirror of
https://github.com/luongnv89/claude-howto.git
synced 2026-09-22 01:10:42 +02:00
feat(zh): add Chinese translations in zh/ directory
Add Chinese (Simplified) translations for all documentation, organized under a dedicated zh/ directory that mirrors the English folder structure. Co-authored-by: tanqingkuang <tanqingkuang@users.noreply.github.com> Translations originally contributed by @tanqingkuang in #45. Restructured from *-CN.md suffix pattern into zh/ directory to prevent the EPUB builder (scripts/build_epub.py collect_folder_files) from picking up Chinese files via glob("*.md") inside module folders.
This commit is contained in:
Luong NGUYEN
@@ -0,0 +1,114 @@
|
||||
---
|
||||
name: DevOps 自动化插件
|
||||
description: 为部署、监控和故障处理提供自动化工作流
|
||||
tags: plugins, devops, automation
|
||||
---
|
||||
|
||||
# DevOps 自动化插件
|
||||
|
||||
完整的 DevOps 自动化工作流，覆盖部署、监控和事故响应。
|
||||
|
||||
## 功能
|
||||
|
||||
✅ 自动化部署
|
||||
✅ 回滚流程
|
||||
✅ 系统健康监控
|
||||
✅ 事故响应工作流
|
||||
✅ Kubernetes 集成
|
||||
|
||||
## 安装
|
||||
|
||||
```bash
|
||||
/plugin install devops-automation
|
||||
```
|
||||
|
||||
## 包含内容
|
||||
|
||||
### Slash 命令
|
||||
- `/deploy` - 部署到生产或预发环境
|
||||
- `/rollback` - 回滚到上一个版本
|
||||
- `/status` - 检查系统健康
|
||||
- `/incident` - 处理生产事故
|
||||
|
||||
### 子 agents
|
||||
- `deployment-specialist` - 部署操作
|
||||
- `incident-commander` - 事故协调
|
||||
- `alert-analyzer` - 系统健康分析
|
||||
|
||||
### MCP 服务器
|
||||
- Kubernetes 集成
|
||||
|
||||
### 脚本
|
||||
- `deploy.sh` - 部署自动化
|
||||
- `rollback.sh` - 回滚自动化
|
||||
- `health-check.sh` - 健康检查工具
|
||||
|
||||
### Hooks
|
||||
- `pre-deploy.js` - 部署前验证
|
||||
- `post-deploy.js` - 部署后任务
|
||||
|
||||
## 使用
|
||||
|
||||
### 部署到预发环境
|
||||
|
||||
```
|
||||
/deploy staging
|
||||
```
|
||||
|
||||
### 部署到生产环境
|
||||
|
||||
```
|
||||
/deploy production
|
||||
```
|
||||
|
||||
### 回滚
|
||||
|
||||
```
|
||||
/rollback production
|
||||
```
|
||||
|
||||
### 检查状态
|
||||
|
||||
```
|
||||
/status
|
||||
```
|
||||
|
||||
### 处理事故
|
||||
|
||||
```
|
||||
/incident
|
||||
```
|
||||
|
||||
## 要求
|
||||
|
||||
- Claude Code 1.0+
|
||||
- Kubernetes CLI（kubectl）
|
||||
- 已配置集群访问
|
||||
|
||||
## 配置
|
||||
|
||||
设置 Kubernetes 配置：
|
||||
|
||||
```bash
|
||||
export KUBECONFIG=~/.kube/config
|
||||
```
|
||||
|
||||
## 示例工作流
|
||||
|
||||
```
|
||||
用户：/deploy production
|
||||
|
||||
Claude:
|
||||
1. 运行 pre-deploy hook（验证 kubectl 和集群连接）
|
||||
2. 将部署委派给 deployment-specialist subagent
|
||||
3. 运行 deploy.sh 脚本
|
||||
4. 通过 Kubernetes MCP 监控部署进度
|
||||
5. 运行 post-deploy hook（等待 pods 就绪，执行 smoke tests）
|
||||
6. 提供部署总结
|
||||
|
||||
结果：
|
||||
✅ 部署完成
|
||||
📦 版本：v2.1.0
|
||||
🚀 Pods：3/3 已就绪
|
||||
⏱️ 用时：2m 34s
|
||||
```
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: alert-analyzer
|
||||
description: 分析监控告警和系统指标
|
||||
tools: read, grep, bash
|
||||
---
|
||||
|
||||
# 告警分析器
|
||||
|
||||
分析系统健康状况和告警：
|
||||
- 告警关联分析
|
||||
- 趋势分析
|
||||
- 根因识别
|
||||
- 指标可视化
|
||||
- 主动问题检测
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: deployment-specialist
|
||||
description: 处理所有部署操作
|
||||
tools: read, write, bash, grep
|
||||
---
|
||||
|
||||
# 部署专家
|
||||
|
||||
部署运维专家：
|
||||
- 蓝绿部署
|
||||
- 金丝雀发布
|
||||
- 回滚流程
|
||||
- 健康检查
|
||||
- 数据库迁移
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: incident-commander
|
||||
description: 协调事故响应
|
||||
tools: read, write, bash, grep
|
||||
---
|
||||
|
||||
# 事故指挥官
|
||||
|
||||
管理事故响应：
|
||||
- 严重性评估
|
||||
- 团队协调
|
||||
- 状态更新
|
||||
- 解决跟踪
|
||||
- 事后复盘推动
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: Deploy
|
||||
description: 将应用部署到生产或预发环境
|
||||
---
|
||||
|
||||
# 应用部署
|
||||
|
||||
执行部署工作流：
|
||||
|
||||
1. 运行部署前检查
|
||||
2. 构建应用
|
||||
3. 运行测试
|
||||
4. 部署到目标环境
|
||||
5. 运行健康检查
|
||||
6. 在 Slack 上通知团队
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
name: Incident Response
|
||||
description: 使用结构化响应流程处理生产事故
|
||||
---
|
||||
|
||||
# 事故响应
|
||||
|
||||
结构化事故响应工作流：
|
||||
|
||||
1. 创建事故记录
|
||||
2. 评估严重性和影响
|
||||
3. 通知值班团队
|
||||
4. 收集诊断信息
|
||||
5. 协调响应工作
|
||||
6. 记录解决方案
|
||||
7. 安排事后复盘
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: Rollback
|
||||
description: 回滚到上一次部署
|
||||
---
|
||||
|
||||
# 回滚部署
|
||||
|
||||
回滚到之前的稳定版本：
|
||||
|
||||
1. 确认上一次部署
|
||||
2. 验证回滚目标健康状态
|
||||
3. 执行回滚流程
|
||||
4. 运行健康检查
|
||||
5. 通知团队
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: System Status
|
||||
description: 检查整体系统健康状况
|
||||
---
|
||||
|
||||
# 系统状态检查
|
||||
|
||||
检查所有服务的系统健康状况：
|
||||
|
||||
1. 查询 Kubernetes pod 状态
|
||||
2. 检查数据库连接
|
||||
3. 监控 API 响应时间
|
||||
4. 查看错误率
|
||||
5. 检查资源利用率
|
||||
6. 报告整体健康状况
|
||||
Reference in New Issue
Block a user