Stats
Actions
Tags
From pm-engineering
Parses error logs, stack traces, and crash reports into a structured root cause diagnosis with confidence level, affected code path, and concrete fix suggestions. Best for debugging exceptions, crashes, or unexpected errors.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-engineering:debugging-log-analyserThe summary Claude sees in its skill listing — used to decide when to auto-load this 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.
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.
Ask for these if not provided:
Error type: [Runtime exception / Build error / Config error / Network error / Memory error / Unknown] Severity: [Fatal / Critical / Warning / Informational] Recurrence pattern: [One-off / Intermittent / Consistent / On-startup / Under load]
Walk the stack frame by frame, starting from the origin:
For each significant frame, note whether it is:
Probable root cause: [1–2 sentence plain English statement] Confidence: [High / Medium / Low — and why] Alternative causes to rule out: [If confidence is not high]
Entry point: [Where the triggering call began] Key function(s) involved: [Specific functions/methods named in the trace] Data that triggered it: [If inferable from the log — e.g. null value, malformed JSON]
Provide a concrete, code-level suggestion:
If the root cause is uncertain, provide an ordered list of 3–5 specific debugging actions:
strace, pprof, --verbose, add logging at X]One or two concrete things that would prevent this class of error recurring:
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-engineeringParses error messages, traces execution through stack traces, correlates logs to identify failure points, and applies systematic hypothesis-driven debugging to isolate and resolve bugs.
Detects and diagnoses application failures by analyzing error logs, stack traces, and system state. Useful when debugging crashes or production incidents.
Traces root causes of errors, stack traces, test failures, and build issues by gathering evidence, following call chains backward, and explaining the full causation narrative in structured format.