Production Incident Responder

Guide production incident response for Kotlin plus Spring services from first alert through mitigation, diagnosis, and follow-up. Use when error rates spike, latency degrades, capacity saturates, a bad deploy or config change is suspected, or the team needs reversible mitigation first and deeper root-cause work second.

398 stars 35 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add JetBrains/skills --skill production-incident-responder
Manual install
git clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/production-incident-responder ~/.claude/skills/production-incident-responder

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Production Incident Responder

Source mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-24`).

## Mission

Restore service safely before chasing perfect explanations.
Keep mitigation, diagnosis, communication, and evidence preservation disciplined and explicit.

## First Principles

- Mitigate first.
- Prefer reversible actions over heroic code changes.
- Preserve evidence while the system is still exhibiting the problem.
- Separate confirmed facts from working hypotheses.

## Inputs To Gather

- Current alert state, user impact, and blast radius.
- Recent deploys, config changes, feature-flag changes, and dependency incidents.
- Key dashboards: latency, error rate, saturation, dependency health, queue depth, pool usage.
- Correlated traces and logs for the failing path.
- Known runbooks, rollback mechanisms, and feature flags.

## Response Sequence

1. State impact and likely severity.
2. Stop unsafe changes and identify the fastest reversible mitigation:
   - rollback
   - disable feature
   - reduce concurrency
   - shed load
   - rate-limit callers
   - isolate or degrade a dependency
3. Preserve high-signal evidence while the symptom still exists.
4. Compare timeline of incident onset with recent changes.
5. Localize the failing layer: application, database, downstream dependency, queue, infrastructure, or configuration.
6. Propose long-term corrective actions only after the service is stable.

## Advanced Incident Heuristics
Read the full skill on GitHub

Details

Skill name
production-incident-responder
Path
production-incident-responder/SKILL.md
Repo updated
21 October 2026

FAQ

What does the Production Incident Responder skill do?

Guide production incident response for Kotlin plus Spring services from first alert through mitigation, diagnosis, and follow-up. Use when error rates spike, latency degrades, capacity saturates, a bad deploy or config change is suspected, or the team needs reversible mitigation first and deeper root-cause work second.

How do I install the Production Incident Responder skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill production-incident-responder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Production Incident Responder popular?

It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.

Related skills

Deploy to Vercel

398

JetBrains/skills

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

DevOps & CloudIn 2 lists35

Vercel React Native Skills

398

JetBrains/skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Mobile DevelopmentIn 2 lists35

Vitest

398

JetBrains/skills

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

Testing & QA35

Sourcecraft Publisher

236

artwist-polyakov/polyakov-claude-skills

Publish static page artifacts to SourceCraft Sites (Yandex infrastructure, works in Russia), with advisory image optimization and an original-image path. Use when a static page/React artifact needs to be deployed to SourceCraft under YYYY/YYYY-MM/page-slug directory layout.

DevOps & Cloud59

Observability Integrator

398

JetBrains/skills

Design actionable observability for Kotlin plus Spring services across logs, metrics, tracing, and health endpoints. Use when instrumenting a service, improving incident diagnosis, defining SLO-driven metrics and alerts, adding trace propagation, controlling metric-cardinality cost, or ensuring async and coroutine flows remain observable in production.

DevOps & Cloud35

Ssh Remote Connection

236

artwist-polyakov/polyakov-claude-skills

SSH connection to remote servers. Use when you need to execute commands on a remote server, check logs, restart services, or manage Docker containers.

DevOps & Cloud59

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.