Skip to content

hoavdc/CodexKit / skills/codexkit-incident-postmortem

codexkit-incident-postmortem

Verified

Write blameless incident postmortems following Google SRE methodology. Covers timeline reconstruction, root cause analysis (5 Whys), impact assessment, and action items with owners. Use after production incidents, outages, or significant bugs to prevent recurrence.

FileKindSize
SKILL.mdskill md5.5 KB
agents/openai.yamlconfig166 B
examples/common-mistakes.mdmarkdown794 B
examples/good-output.mdmarkdown958 B
verification/checklist.mdmarkdown1.3 KB

verification/checklist.md

View on GitHub
# 4C Verification Checklist — Incident Postmortem

> Use this checklist after generating output. Answer each question honestly.

## Correctness — Is it right?

- [ ] Timeline events are verified against logs, not memory alone
- [ ] 5 Whys reaches a systemic cause, not an individual's mistake
- [ ] Impact numbers (users, duration, revenue) come from monitoring data

## Completeness — Is it done?

- [ ] Timeline covers detection → response → resolution → follow-up
- [ ] Action items have types (prevent / detect / mitigate), owners, and deadlines
- [ ] Contributing factors include both technical and process gaps

## Context-fit — Does it match?

- [ ] Postmortem depth is proportional to incident severity (SEV1 gets full analysis)
- [ ] Language is blameless — no individual named as the cause
- [ ] Audience can understand without deep system knowledge

## Consequence — Is it safe to use?

- [ ] If none of the action items were completed, how likely is recurrence?
- [ ] Is there a single action item that would prevent 80% of similar incidents?
- [ ] If this postmortem were published externally, would it be embarrassing?

---

**Final question:** _If this output were used immediately in production, what is the single biggest risk?_

Write the answer here before considering the skill output complete.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall