postmortem-write

To write a blame-free incident postmortem document, analyze incident details and git logs to construct a timeline, perform root cause analysis, and outline actionable preventative measures. This approach focuses purely on technical and process improvements rather than individual blame.

Automating root cause analysis using git logs involves parsing commit diffs from a specified range to reconstruct the incident timeline. It then applies the 5 Whys technique to systematically identify underlying technical causes and generate categorized preventative measures.

Structuring an incident response RCA with the 5 Whys technique requires building a chronological incident timeline from logs, then iteratively asking why failures occurred. This isolates the root cause to generate concrete, assignable preventative action items.

You can generate actionable preventative measures by providing a specific commit range representing the incident. The system analyzes the resulting diffs and logs to break down resolutions into concrete, categorized action items for preventing future recurrence.

Effective postmortem generation explicitly works without assigning individual blame by focusing strictly on technical and process failures. It ensures documentation captures systemic root causes and actionable improvements rather than targeting personal mistakes.