incident-response-and-debugging

Diagnose production incidents using phased response protocols and debugging techniques.

Updated Mar 8, 2026

Search Tags:#debugging #troubleshooting #post-mortem #incident response #runbook #production support

Ready to run

npx skills add https://github.com/Jaydpatel01/.github --skill incident-response-and-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response-and-debugging
Source: https://github.com/Jaydpatel01/.github/tree/main/skills/incident-response-and-debugging
Command: npx skills add https://github.com/Jaydpatel01/.github --skill incident-response-and-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework and practical tools to systematically diagnose and resolve production incidents, minimizing user impact and preventing recurrence.

Core Features & Use Cases

Incident Management Framework: Guides users through detection, containment, diagnosis, resolution, and post-incident review.
Debugging Techniques: Offers practical commands and strategies for log analysis, database diagnostics, memory leak detection, and distributed system debugging.
Runbook Templates: Provides pre-defined templates for common incident scenarios like service outages and high error rates.
Use Case: When a critical service alert fires, this Skill helps you quickly classify severity, contain the issue, identify the root cause using provided debugging commands, and document the incident for future learning.

Quick Start

Use the incident-response-and-debugging skill to diagnose a production incident by following the incident response phases.

Frequently Asked Questions about incident-response-and-debugging

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

FAQPage Schema

What is the best way to handle production support and resolve incidents fast?▼

Production support and incident response require a structured framework covering detection, containment, diagnosis, resolution, and post-incident review to systematically minimize user impact and prevent recurrence.

How do I debug production incidents in distributed systems?▼

Debugging production incidents in distributed systems involves applying systematic debugging techniques, including log analysis, database diagnostics, and memory leak detection, to accurately identify and resolve the root cause.

How do I classify incident severity during a service outage?▼

Classifying incident severity is the first step in the incident response protocol, allowing you to accurately categorize the impact of a service outage and determine the appropriate containment and resolution strategy.

What should be included in a post-mortem after troubleshooting an incident?▼

A post-mortem after troubleshooting an incident should document the incident timeline, root cause analysis, resolution steps, and preventive measures to ensure future learning and avoid recurrence.

Can I use runbook templates for high error rates and service outages?▼

Pre-defined runbook templates provide structured, ready-to-use protocols for common scenarios like high error rates and service outages, guiding you through containment and diagnosis to ensure safe and fast resolution.

What techniques work for performance debugging and memory leak detection in production?▼

Performance debugging and memory leak detection in production rely on systematic diagnostic techniques, utilizing specific commands for log analysis and database diagnostics to isolate and resolve underlying system issues.