---
title: "Production Incident Responder: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/jetbrains-production-incident-responder/
description: "Runs production incident response as mitigate-first: state impact, pick the fastest reversible mitigation, preserve evidence while the symptom still exists, then diagnose — with heuristics for retry storms, cache stampedes and config-only regressions."
---

# Production Incident Responder: review, setup & limitations · Undominated.ai

> Runs production incident response as mitigate-first: state impact, pick the fastest reversible mitigation, preserve evidence while the symptom still exists, then diagnose — with heuristics for retry storms, cache stampedes and config-only regressions.

[← Explore all skills](/skills/)

CLOUD OPERATIONS / JetBrains

# Production Incident Responder

Runs production incident response as mitigate-first: state impact, pick the fastest reversible mitigation, preserve evidence while the symptom still exists, then diagnose — with heuristics for retry storms, cache stampedes and config-only regressions.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/JetBrains/skills/tree/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/production-incident-responder)

SOURCE REVIEW

 Reviewed 2026-10-13
 Evidence 6 linked sources
 Publisher JetBrains
 Licence [MIT (upstream Kotlin backend agent skills) ↗](https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE)
 Revision e0f258b5cfed
 [Read what was—and wasn’t—checked ↓](#review)

“Guide production incident response for Kotlin plus Spring services from first alert through mitigation, diagnosis, and follow-up.”

 [JetBrains · upstream description ↗](https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/production-incident-responder/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Orders the response deliberately — reversible mitigation before root-cause work — and names the anti-patterns: reflexive restarts that destroy evidence and amplify connection storms, scaling the app tier when the database is the bottleneck.
- The heuristics name specific failure patterns: a healthy dependency at low volume failing under your own fleet's retry storm, config-only incidents masquerading as code regressions, rollback being unsafe after data shape has changed.
- The output contract separates confirmed facts from working hypotheses and requires impact, mitigation, evidence and next diagnostic step.

### A good fit for

 - Responding to an error-rate spike, latency degradation or capacity saturation
- Choosing between rollback, feature-flag disable, load shedding and rate limiting
- Preserving evidence and the incident timeline for the later postmortem

### Weigh up before choosing

 - Framed for Kotlin plus Spring services; the response sequence is stack-generic but dashboard and tooling references assume JVM-ecosystem observability.
- No references or runbook templates — the skill is a response discipline, so the project's dashboards, rollback mechanisms and feature flags must already exist.
- Mitigation ordering is heuristics, not a decision procedure; a human incident commander still owns the call.
- The author: Kotlin credit is added by the JetBrains mirror. The upstream SKILL.md names no author, and the upstream repository now sits under the personal account yalishevant with an MIT licence naming Anton Yalyshev.
- The JetBrains/skills README disclaims the catalogue as provided for demonstration and educational purposes only and asks you to test each skill before relying on it.
- The upstream repository moved: https://api.github.com/repos/Kotlin/kotlin-backend-agent-skills now returns yalishevant/kotlin-backend-agent-skills, a personal account (checked 2026-10-13). The pins and the MIT licence are unchanged.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - production-incident-responder/SKILL.md (JetBrains mirror, complete, 96 lines)
- production-incident-responder/agents/openai.yaml (identical to upstream)
- upstream yalishevant/kotlin-backend-agent-skills production-incident-responder SKILL.md
- upstream yalishevant/kotlin-backend-agent-skills LICENSE
- JetBrains/skills README mirror policy
- https://github.com/Kotlin/kotlin-backend-agent-skills (answers HTTP 301 to yalishevant/kotlin-backend-agent-skills)
- mirror SKILL.md diffed against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e

### Our findings

 - First principles make mitigation reversible-action-first and evidence preservation an explicit step before diagnosis begins.
- Guardrails forbid code changes as the first incident action when a reversible mitigation exists, and root-cause certainty without evidence.
- A diff against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e shows the mirror adds four frontmatter lines (metadata, short-description, author: Kotlin, source) and nothing else; the upstream file has no author field. agents/openai.yaml is identical in both.
- Upstream health: https://github.com/Kotlin/kotlin-backend-agent-skills, which the mirror’s metadata.source and README name, now answers HTTP 301 to yalishevant/kotlin-backend-agent-skills, a personal account (https://api.github.com/repos/Kotlin/kotlin-backend-agent-skills returns full_name yalishevant/kotlin-backend-agent-skills, owner type User). fd0ed521d22efd28221d532c9abab97af0b9bf0e is still that repository’s head, and its LICENSE (MIT, copyright 2026 Anton Yalyshev) is unchanged (checked 2026-10-13).

### Not established by this review

 - No incident was responded to and no mitigation was executed; the workflow was read, not run.
- Heuristic claims about retry storms and cache stampedes were not reproduced.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md)

DOCUMENTED COMMAND

 npx skills add JetBrains/skills/production-incident-responder --skill production-incident-responder Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/JetBrains/skills/tree/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/production-incident-responder --skill production-incident-responder Copy reviewed-revision command ↗ - Install the complete skill directory; the agents profile travels with the SKILL.md.
- Bring the alert state, dashboards and recent-change timeline; expect a mitigation-first response with an explicit evidence and hypothesis log.

### Before you start

 - Node.js/npm for the installer
- An agent that supports the Agent Skills format
- Access to alerts, dashboards, traces and the project's rollback or feature-flag mechanisms

### Compatibility

Agent Skills-compatible coding agents · Any production service with alerts, dashboards and a rollback path · Kotlin plus Spring framing adapts to other stacks

### Reads dashboards, logs and deploy state; proposes mitigations

 - Read alert state, dashboards, traces, logs and recent deploy history
- Draft mitigation steps, timelines and follow-up actions
- Executing mitigations on production remains the user's decision, not the skill's

### Cost model

MIT-licensed instruction package; production actions it proposes carry their own operational risk.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition at reviewed revision ↗](https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/production-incident-responder/SKILL.md) Checked 2026-10-13 https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/production-incident-responder/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
- [Upstream skill definition (Kotlin backend agent skills origin) ↗](https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/.agents/skills/production-incident-responder/SKILL.md) Checked 2026-10-13 https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/.agents/skills/production-incident-responder/SKILL.md Supports: review, limitations
- [Upstream licence (MIT) ↗](https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE) Checked 2026-10-13 https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE Supports: license
- [Former upstream location (HTTP 301 to yalishevant/kotlin-backend-agent-skills) ↗](https://github.com/Kotlin/kotlin-backend-agent-skills) Checked 2026-10-13 https://github.com/Kotlin/kotlin-backend-agent-skills Supports: review, limitations
- [Mirror policy: JetBrains-filtered, JetBrains-verified snapshot with source links and CI skill scanning ↗](https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/README.md) Checked 2026-10-13 https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/README.md Supports: review, install, limitations
- [Skills installer source formats and selective installation ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md) Checked 2026-10-13 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md Supports: install

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Microsoft Azure Diagnostics ↗ Routes Azure incidents through resource health, recent changes, logs and service-specific troubleshooting guides.](/skills/microsoft-azure-diagnostics/)[### AKS Automatic Readiness ↗ Pins Microsoft's AKS Automatic readiness skill, which assesses a cluster or local manifests without changing the cluster and writes files only after an accepted diff.](/skills/microsoft-azure-kubernetes-automatic-readiness/)[### Azure Deploy ↗ Pins Microsoft's Azure deploy skill, which stops unless a separate validation skill has already marked the deployment plan validated.](/skills/microsoft-azure-deploy/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
