incident

Guide production incident response through detection, triage, mitigation, and post-mortem analysis.

77|4|Updated Jun 20, 2022
One-click install
npx skills add https://github.com/htlin222/dotfiles --skill incident-htlin222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills/incident
Command: npx skills add https://github.com/htlin222/dotfiles --skill incident-htlin222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured and efficient workflow for responding to and resolving production incidents, minimizing downtime and impact.

Core Features & Use Cases

  • Systematic Incident Handling: Guides users through detection, triage, mitigation, resolution, and review.
  • Command Snippets: Offers practical bash commands for common debugging and mitigation tasks.
  • Templates: Includes templates for incident communication and post-mortems.
  • Use Case: When the production API starts returning 500 errors, this Skill can be used to quickly check logs, identify the failing component, and initiate a rollback or scaling action.

Quick Start

Use the incident skill to begin investigating a production outage.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I handle production incidents systematically from detection to post-mortem?

Production incidents are handled systematically by following a structured workflow for detection, triage, mitigation, resolution, and post-mortem analysis. This includes using predefined severity levels and communication templates to ensure rapid response.

What is the process for triaging production issues and initiating a rollback?

Triage production issues by checking logs with practical bash commands to identify failing components. Once identified, initiate mitigation actions such as a rollback or scaling action to rapidly address the system failure.

Are there templates available for incident communication and post-mortem analysis?

Yes, templates for incident communication and post-mortems are included. They provide structured formats to document mitigation efforts, resolution steps, and review critical system failures effectively.

Can I use this for debugging API performance degradations and 500 errors?

Yes, debugging API performance degradations and 500 errors is a core use case. It guides you to quickly check logs, identify the failing component, and execute mitigation commands for rapid resolution.

What's the best way to prepare for SRE incident response in production?

Prepare for SRE incident response by leveraging predefined severity levels and actionable command snippets. This facilitates rapid response to critical system failures and minimizes production downtime.