Individual skill
incident-postmortem
撰写结构化的故障复盘或事后回顾。当被要求写故障复盘、故障报告、P1 / P2 回顾、宕机报告或根因分析(RCA)时使用。产出不指责个人的复盘文档:时间线、根本原因、促成因素、影响摘要和行动项。项目或活动的复盘请使用 cn-fupan。
skills-i18n/zh/incident-postmortem/SKILL.md
Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,542
- Repository last updated
- Nov 11, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- product-management Repository topic
- productivity Repository topic
- skills Repository topic
- claude-skills Repository topic
- agent-skills Repository topic
- chatgpt Repository topic
- claude-code Repository topic
- cursor Repository topic
- gemini Repository topic
- prompt-engineering Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,760 bytes
Read excerpt
> [incident-postmortem](../../../skills/incident-postmortem/SKILL.md) 的简体中文翻译,英文版本为规范版本。
# 故障复盘
这个技能按行业标准格式,产出一份完整、不指责个人的故障复盘文档。产出始终坚持不指责的框架(关注系统缺口而不是个人失误),并推动形成具体、可关闭的行动项,而不是含糊的流程承诺。
## 提议的操作
行动项不必只停留在纸面上:把它们交给 [`action-runner`](../../../skills/action-runner/SKILL.md),它会先预览(试运行、标注风险),只通过已连接的操作类 MCP 执行你批准的内容,并把做过的事记回大脑。典型做法:**为每个行动项建一个跟进任务**(🟡),分配给负责人并设截止日期。这个技能只提议;由 action-runner 把关并执行,绝不悄悄进行。
## 它在流程中的位置:把故障变成修复
故障响应主线的第三步:**`/slo-error-budget`(框定)→ `/debugging-log-analyser` → `incident-postmortem` → `/oncall-runbook`**。它从 `/debugging-log-analyser` 接收**根因诊断**(读它,而不是重新诊断),并把**促成因素和按优先级排列的行动项**交给 `/oncall-runbook`;`/slo-error-budget` 的错误预算决定这些行动有多紧急。*不指责*、*根本原因与促成因素*和*行动项*统一定义在 [`docs/craft/incident-response.md`](../../../docs/craft/incident-response.md);不指责是承重的规则。