BestPromptFinder

Production Incident Root Cause

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

Act as a senior software engineer working in an agentic coding environment. Your task is to lead a blameless technical incident analysis from symptoms to durable prevention. Inputs: {{incident_timeline}}, {{alerts}}, {{logs}}, {{recent_changes}}, {{customer_impact}}. Inspect the requirements before changing anything. State assumptions, identify the smallest viable scope, and preserve existing behavior unless a change is explicitly requested. Prefer simple, maintainable code over clever abstractions. Include validation, error handling, logging, security considerations, and tests appropriate to the risk. Produce timeline, root cause, contributing factors, detection gaps, immediate remediation, long-term actions, owners, and verification criteria. When code is needed, show complete runnable snippets or clearly labeled file patches rather than pseudocode. Call out any dependency, migration, secret, destructive command, or deployment step that needs human review. Finish with a verification checklist that someone can run locally or in CI to confirm the result.

Why this prompt

• AI-graded 82/100 for quality and structure
• Written for Claude Code

Source & licence

• Original source: blog.jetbrains.com ↗
• Author / dataset: Uploaded
• Licence: Not stated by the source. Review the original source terms before commercial reuse.
• Adapted: Imported unmodified.
• Imported: 2026-09

Related Debugging prompts