Coding & Debugging Prompts
Production Code-Path Reconstructor
Reconstruct the code path behind a production incident by correlating requests, releases, traces, logs, configuration, and side effects.
FreeClaudeChatGPT
Best for
Incident responders and software teams tracing production-only failures across multiple services and asynchronous boundaries.
Suitable LLM groups
FrontierReasoning
Prompt
You are a production debugging lead who specializes in reconstructing failures across distributed application code paths.
Inputs:
1. Incident symptom, impact, and timeline: {{incident}}
2. Architecture and relevant repositories or services: {{system_context}}
3. Logs, traces, metrics, errors, and user reports: {{evidence}}
4. Deployments, flags, configuration, and dependency changes: {{changes}}
5. Access, safety, and recovery constraints: {{constraints}}
Do the following:
1. Establish a fact-only timeline and correlate identifiers across gateway, service, queue, database, and external-system evidence.
2. Reconstruct the most likely executed code path, including feature-flag branches, retries, fallbacks, exception handling, and asynchronous side effects.
3. Mark each transition as confirmed, inferred, contradicted, or unknown, and rank alternative paths that still fit the evidence.
4. Identify the earliest faulty decision or state change, distinguish trigger from underlying defect, and propose targeted evidence collection or reproduction steps.
5. Deliver a code-path narrative, evidence table, leading root-cause hypothesis, immediate containment, minimal repair, regression test, and observability gaps. Avoid changing production data merely to test a hypothesis.How to use
- Use a shared time zone for all evidence.
- Include correlation IDs and deployment versions.
- Separate verified events from team assumptions.
- Preserve evidence before restarting or redeploying systems.
Example input
Incident: 146 customers received duplicate renewal emails between 09:03 and 09:18 UTC. Context: scheduler publishes renewal jobs, notification service sends email, and delivery IDs are stored in PostgreSQL. Evidence: queue shows redelivery after 30-second visibility timeout; email provider p95 rose to 38 seconds; traces end before provider response. Changes: notification timeout increased from 20 to 45 seconds, but queue visibility stayed at 30 seconds. Constraints: sending is paused; database records must not be manually edited.
Example output
The confirmed timeline shows jobs became visible again at 30 seconds while the first worker still waited up to 45 seconds for the provider. A second worker then processed the same job before the delivery record was committed. The provider slowdown triggered the incident, but the underlying defect is mismatched timeout and idempotency boundaries. Containment keeps renewal sending paused; the repair adds a provider idempotency key and makes queue visibility exceed the bounded processing timeout. A regression test simulates a 38-second provider response and redelivery.
Customization tips
- — Include feature-flag and configuration history.
- — Map asynchronous side effects and retry boundaries.
- — State which production actions are prohibited.
- — Add missing trace spans to the remediation plan.
Tags
#production-debugging#incident-analysis#distributed-tracing#code-path-analysis#root-cause-investigation
FAQ
What is this prompt for?
It reconstructs the exact or most plausible application path that produced a production incident.
How should I customize it?
Provide synchronized evidence, architecture, deployment and flag history, correlation IDs, relevant code, and operational constraints.
Are there any limitations?
Missing logs or traces can prevent a definitive reconstruction, so some transitions may remain explicitly labeled as inferred.
How is it different from a basic prompt?
It correlates evidence across distributed boundaries, rates every path transition by confidence, and separates the incident trigger from the latent defect.
Related Prompts
All Coding & Debugging prompts →Free
Root Cause Bug Investigator
Guides a systematic investigation of a bug from symptom to root cause, avoiding quick patches that mask the real problem, and produces a targeted fix.
ClaudeChatGPT
#debugging#root-cause-analysis#bug-fixing
Free
Concurrency and Race Condition Investigator
Reconstruct intermittent concurrency failures using timelines, shared state, synchronization rules, and controlled reproduction experiments.
ClaudeChatGPT
#race-condition#concurrency-debugging#deadlock-analysis
Free
Flaky Test Root Cause Analyzer
Investigate nondeterministic tests by classifying failure patterns, controlling hidden inputs, and designing a reproducible fix.
ClaudeChatGPT
#flaky-tests#test-reliability#nondeterminism
Related Skills
Code ImprovementFree
Debugging and Root Cause Analyst
Investigate software defects systematically using evidence, hypotheses, reproduction, instrumentation, isolation, and verification.
ClaudeChatGPTCursor
#debugging#root cause analysis#bug investigation
Testing & Quality ChecksFree
Observability and Incident Diagnostics Designer
Design logs, metrics, traces, alerts, dashboards, SLOs, and runbooks that support fast diagnosis and reliable incident response.
ClaudeChatGPTCursor
#observability#incident response#metrics
Related articles coming soon — visit the Learn hub.