incident-response

Automate incident response planning and post-mortem documentation for Python/React applications.

8|1|Updated Feb 3, 2026

Search Tags:#post-mortem #PostgreSQL #FastAPI #runbook #triage #incident #incident-response

Ready to run

npx skills add https://github.com/hieutrtr/ai1-skills --skill incident-response-hieutrtr

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, grep, curl, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Production incident response procedures for Python/React applications. Use when responding to production outages, investigating error spikes, diagnosing performance degradation, or conducting post-mortems. Covers severity classification (SEV1-SEV4), incident commander role, communication templates, diagnostic commands for FastAPI/PostgreSQL/Redis, rollback procedures, and blameless post-mortem process. Does NOT cover monitoring setup (use monitoring-setup) or deployment procedures (use deployment-pipeline).

Core Features & Use Cases

Structured incident response runbooks and post-mortems to reduce mean time to recovery.
Templates for incident commander roles, escalation, and external communications.
Command references for triage and diagnostics across FastAPI, PostgreSQL, and Redis.

Quick Start

Activate this skill during an incident to access runbooks and templates, and generate post-mortems.

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I respond to a production outage in a FastAPI and PostgreSQL application?▼

Incident response for a FastAPI and PostgreSQL production outage involves activating a structured runbook to triage the issue, executing diagnostic commands, and following an incident commander protocol to reduce mean time to recovery. It provides severity classification and rollback procedures.

What is a blameless post-mortem and how do I document one for an error spike?▼

A blameless post-mortem is a structured document created after an error spike or outage to analyze root causes without attributing fault. This process uses provided templates to guide evidence gathering, document timelines, and generate actionable remediation items.

Can I use these incident runbooks for Python applications using Redis?▼

Yes, the incident runbooks are designed for Python applications and include specific diagnostic command references for Redis, alongside FastAPI and PostgreSQL. This allows you to triage latency issues and performance degradation across your entire application stack.

What's the best way to classify incident severity during a latency issue?▼

Classifying incident severity during a latency issue uses a SEV1 through SEV4 framework to categorize impact levels. This classification determines the required escalation paths, communication templates, and the specific diagnostic commands needed for the response.

Does this cover monitoring setup and deployment procedures for production incidents?▼

No, this does not cover monitoring setup or deployment procedures. It focuses strictly on active incident response, triage, and post-mortem documentation, relying on separate monitoring-setup and deployment-pipeline processes for those specific functions.