debug

To find the root cause of production incidents, capture error evidence from logs, isolate the scope using request_id and time windows, form hypotheses, and validate them with targeted commands to generate a structured Debug Report.

The best way to debug test failures is using an evidence-first workflow that inspects logs, detects error patterns, proposes hypotheses, tests them with concrete command-based validation, and applies minimal fixes to prevent regressions.

To systematically fix application crashes and stack trace errors, analyze the failing stack trace, search relevant logs for error patterns, validate 2-3 hypotheses with targeted commands, and apply the smallest fix before verifying the outcome.

Yes, you can use this evidence-first workflow to diagnose timeout, connection, and resource-limit issues like OOM by cross-correlating system logs and applying structured command-based validation to verify the root cause.

You document root cause analysis for postmortems by generating a structured Debug Report that includes the Issue, Root Cause, Evidence, Fix, Verification, and Prevention steps derived from the systematic debugging workflow.

When logs show error spikes without a clear failure point, isolate the scope by cross-correlating request_id and time windows, test hypotheses with concrete commands, and output a Debug Report to pinpoint the minimal fix.