Debugging Log Analyser Skill

Parses raw error logs, stack traces, and crash reports into a structured diagnosis with probable root cause, affected code path, and specific next steps — no hand-waving.

Where this sits — the diagnosis step

Second in the incident-response spine: /slo-error-budget (frame) → debugging-log-analyser → /incident-postmortem → /oncall-runbook. It takes the raw symptoms of a live incident and hands /incident-postmortem the root-cause diagnosis and the fix — so the postmortem builds on the diagnosis instead of re-deriving it. Shared terms (root cause vs contributing factors, mitigation vs resolution) are defined once in docs/craft/incident-response.md.

The loop

Debugging fails when it jumps to a fix before the evidence supports it. Phase 2 is the skill — a diagnosis is only as good as its confidence, and false certainty sends responders down the wrong path at the worst time.