runbook

Solid

引導 Runbook 的撰寫、維護與演練。 Use when: 撰寫 Runbook、規劃演練、稽核 Runbook 覆蓋範圍、事故後更新 Runbook。 Not for: 處理正在進行中的事故——請用 /incident；部署程序本身——請用 /deploy。 Keywords: runbook, operations, drill, on-call, procedure, 維運手冊, 演練, 待命, 標準程序.

Code & Development 71 stars 13 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 79/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Runbook 助手 > **語言**: [English](../../../../skills/runbook-assistant/SKILL.md) | 繁體中文引導 Runbook 撰寫、維護、演練和覆蓋率報告。 ## 功能 | 功能 | 說明 | |------|------| | **建立 Runbook** | 從標準範本產生 Runbook（7 個區段） | | **演練規劃** | 規劃和記錄演練 | | **覆蓋率報告** | 檢查 P1-P4 告警的 Runbook 覆蓋率 | | **品質審查** | 驗證 Runbook 品質（6 個原則） | | **過期檢查** | 識別過期需審查的 Runbook | ## 使用方式 ```bash /runbook # 顯示 Runbook 指南 /runbook create "api-latency-high" # 為告警建立 Runbook /runbook drill # 規劃演練 /runbook coverage # 產生覆蓋率報告 ``` ## 下一步引導 > **Runbook 引導完成。建議下一步：** > - 執行 `/observability --alerting` 連結告警到 Runbook ⭐ **推薦** > - 執行 `/incident --postmortem` 從事故更新 Runbook > - 執行 `/checkin` 提交變更 ## 參考 - 核心規範：[runbook-standards.md](../../../../core/runbook-standards.md) - 相關：[alerting-standards.md](../../../../core/alerting-standards.md) - 相關：[postmortem-standards.md](../../../../core/postmortem-standards.md)

Details

Author: AsiaOstrich
Repository: AsiaOstrich/universal-dev-standards
Created: 8 months ago
Last Updated: today
Language: JavaScript
License: NOASSERTION

Bundled in these plugins

universal-dev-standards

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Featured

eng-runbook

服务概述 + alerts 表 + dashboards + 操作命令 + on-call + 事故清单

8,379 Updated 3 days ago

nexu-io

AI & Automation Listed

runbook

Write an operational runbook that an on-call engineer can execute at 3am. Use when adding an alert, launching a service, or after an incident exposed a missing procedure.

0 Updated 2 weeks ago

bakhod1r

Code & Development Featured

runbook

Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.

224 Updated today

testdouble