post-mortem

To trace a bug to its root cause using git history, this skill analyzes commits and diffs to identify regression introductions. It follows a phase-based workflow to gather information and construct a timeline of changes.

Generating a structured post-mortem report involves documenting root causes and remediation steps from an incident. This skill produces formal incident reports suitable for sharing with stakeholders during post-incident reviews.

The best way to identify which commit introduced a regression is by tracing commits and analyzing diffs across the git repository. This skill automates regression point identification to pinpoint the exact code change.

Yes, you can use this post-mortem workflow on any git repository. It applies universally to git histories to trace fixes and produce formal incident reports without requiring specific project structures.

A phase-based post-mortem investigation workflow involves three stages: information gathering, timeline construction, and final report generation. It uses git diffs to derive findings and produce a structured post-mortem report.

To document root causes and remediation steps after an incident, this skill generates a structured post-mortem report. It helps teams learn from incidents by formally recording findings to reduce recurrence.