debug-prod-incident

Investigating a production incident involves tracing events across logs, git commits, and deployment data to build an evidence-backed timeline. This skill assembles that timeline, tests root-cause hypotheses against the evidence, and produces a mitigation note for post-mortem handoff.

Finding the root cause of an outage requires correlating error spikes with recent commits and deployments. This skill forms root-cause hypotheses, verifies them against gathered evidence, and proposes mitigations without deploying fixes.

Generating a post-mortem document from incident logs requires assembling a verified timeline and root-cause analysis. This skill produces an incident-history.md entry containing the timeline, hypotheses, and mitigation notes ready for post-mortem review.

An incident timeline helps trace failed scans or webhook errors by chronologically mapping log entries, git history, and deployment events. This skill builds that timeline to assess evidence and propose mitigations for the production incident.

This debugging approach does not deploy fixes automatically during an active incident. It strictly investigates and documents the event by tracing logs and deployments, outputting a root-cause hypothesis and mitigation note for manual handoff.

Tracing a production incident and finding the root cause requires logs, git history, and deployment data. With these inputs, the skill constructs an evidence-backed timeline and generates an incident-history.md entry for post-mortem analysis.