write-a-postmortem

Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use w

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-changelog-update 456,653 ★
  Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified cont
• git-guardrails-claude-code 323,485 ★
  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before t
• pr 323,485 ★
  Use when writing a PR body.
• setup-matt-pocock-skills 323,485 ★
  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain
• setup-pre-commit 323,485 ★
  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use w