One-click install
npx skills add https://github.com/JetBrains/skills --skill production-incident-responder-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-incident-responder
Source: https://github.com/JetBrains/skills/tree/main/production-incident-responder
Command: npx skills add https://github.com/JetBrains/skills --skill production-incident-responder-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide production incident response for Kotlin and Spring services from alert through mitigation and follow-up, ensuring rapid containment and evidence preservation.

Core Features & Use Cases

  • Reversible mitigation playbooks: rollback, feature flag adjustments, and load shedding designed for fast, safe containment.
  • Evidence preservation and coordination: capture timelines, logs, metrics, and traces to enable root-cause analysis after stabilizing the system.
  • Structured incident workflow: define incident severity, owners, and a clear sequence from alert to long-term remediation.
  • Use Case: When an outage occurs after a deployment, apply this skill to stabilize service quickly, preserve evidence, and document next steps.

Quick Start

On incident onset, invoke Production Incident Responder to guide safe mitigation, preserve evidence, and structure the investigation.

Frequently Asked Questions about production-incident-responder

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

FAQPage Schema
How do I handle a production incident for a Spring service after a bad deploy?

Production incident response for Spring services involves applying reversible mitigations like rollbacks or feature flag adjustments to stabilize the system quickly after a bad deploy. This structured workflow ensures safe containment while preserving logs and metrics for later analysis.

What is the best way to preserve evidence during a high-severity outage?

Evidence preservation during an outage requires capturing timelines, logs, metrics, and traces before applying mitigations. This approach ensures the data needed for root-cause analysis remains intact, allowing teams to stabilize the system without losing critical forensic information.

How do I mitigate latency degradation and error rate spikes in Kotlin services?

Mitigating latency degradation and error rate spikes in Kotlin services requires applying reversible actions such as load shedding or configuration rollbacks. This structured response workflow prescribes safe containment steps to restore service stability while capturing evidence for follow-up diagnostics.

Can I use a structured incident response workflow for capacity saturation issues?

A structured incident response workflow effectively manages capacity saturation by defining incident severity, owners, and explicit outputs. It guides teams from alert onset through immediate mitigation and long-term remediation, ensuring coordinated communication and systematic resolution.

When should I use reversible mitigations instead of immediate root-cause fixing?

Reversible mitigations like rollbacks and feature flag adjustments should be used during active high-severity incidents to stabilize the system rapidly. Prioritizing immediate containment over root-cause fixing preserves system health while evidence is collected for subsequent analysis.