hatch3r-incident-response

Coordinate production incident response with severity classification, triage, and post-mortem generation.

26|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-incident-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hatch3r-incident-response
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-incident-response
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-incident-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams respond to production incidents with a structured, repeatable workflow that reduces confusion during triage and ensures corrective actions follow through.

Core Features & Use Cases

  • Structured severity classification (P0–P3) to scope impact and decide how aggressively to act.
  • Stepwise triage and mitigation to identify affected systems, verify stabilization, and prioritize rollback/hotfix decisions.
  • Root-cause and post-mortem production including timelines, action items, and follow-up issue/work-item creation for permanent prevention.
  • Use case: An outage occurs after a deploy; use this Skill to classify severity, determine blast radius, stabilize the service, and then generate a post-mortem with linked follow-up work.

Quick Start

Ask the AI to run an incident response for your production issue, including severity classification, triage, mitigation verification, root-cause analysis, and a post-mortem plus follow-up tickets.

Frequently Asked Questions about hatch3r-incident-response

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

FAQPage Schema
How do I run an incident response triage for a production outage?

Post-mortem generation requires capturing the incident timeline, root cause, and corrective action items. This skill produces definition-of-done post-mortem artifacts and automatically creates linked follow-up issues or work items using your configured git remote platform to prevent recurrence.

How does severity classification work for incident response?

Severity classification scopes incident impact using levels P0 through P3 to decide how aggressively to act. This skill coordinates production incident response by driving this structured classification to determine blast radius and prioritize mitigation efforts.

Can I automate ticket creation for post-mortem follow-up items?

Ticket creation for post-mortem follow-up items is automated by applying the configured git remote platform. This skill inspects and creates related issues or work items to ensure corrective actions follow through after incident stabilization and root-cause analysis.

What is the best way to structure root cause analysis after a deploy causes an outage?

Root cause analysis after a deploy should include timeline reconstruction, impact scoping, and follow-up issue creation. This skill generates post-mortems containing these elements, verifying mitigation and producing definition-of-done artifacts with linked follow-up work for permanent prevention.

Does incident response work with my git remote platform for issue tracking?

Incident response applies to workflows across platforms by using the configured git remote platform. This skill inspects and creates related issues or work items directly through your remote configuration, enforcing ambiguity detection and preventing sensitive data leakage during ticket creation.