debug-prod-incident

Name: debug-prod-incident
Availability: InStock
Author: Flintmere

Trace production incidents into evidence-backed timelines and root-cause hypotheses.

Updated Apr 18, 2026

Search Tags:#debugging #timeline #logs #post-mortem #root-cause #incident

Ready to run

npx skills add https://github.com/Flintmere/flintmere --skill debug-prod-incident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-prod-incident
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/debug-prod-incident
Command: npx skills add https://github.com/Flintmere/flintmere --skill debug-prod-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace-first debugging for a live or recent Flintmere production incident. Use when users report an outage, errors spike in logs, a scan fails at scale, or a payment webhook is delivering errors. Produces a timeline, a root-cause hypothesis verified against evidence, a recommended fix or mitigation, and an incident-history.md entry. Never deploys fixes.

Core Features & Use Cases

Build a comprehensive incident timeline from logs, commits, and deployments.
Form and test root-cause hypotheses against evidence; generate mitigations without deploying fixes.
Produce a post-mortem-ready incident-history.md entry and handoff to the fix surface.

Quick Start

Describe the incident and let the skill assemble a timeline from logs, commits, and deploy data.

Frequently Asked Questions about debug-prod-incident

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate a production incident using logs and git history?▼

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.

What's the best way to find the root cause of an outage or error spike?▼

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.

Can I generate a post-mortem document from incident logs and deployment data?▼

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.

How does an incident timeline help trace failed scans or webhook errors?▼

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.

Does this debugging approach deploy fixes automatically during an active 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.

What data do I need to trace a production incident and find the root cause?▼

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.