debugging-log-analyser
Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace walkthrough, probable root cause with confidence level, affected code path, a concrete code-level fix suggestion, and ordered next debugging steps.
npx skills add mohitagw15856/pm-claude-skills --skill debugging-log-analyser --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## Required Inputs Ask for these if not provided: - **The log / stack trace / error output** (paste directly or describe the error) - **Language and framework** (e.g. Node.js + Express, Python + Django, Java Spring, Go) - **Context** (what changed before this started — e.g. recent deploy, config change, increased traffic, new input data; or "nothing changed" is also useful) - **Frequency** (one-off / intermittent / consistent / regression after a specific change) - **Environment** (local dev / staging / production) - **What they've already tried** (if anything) ## Output Format --- # Debugging Report: [Service/App Name] ### 1. Error Classification **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] ### 2. Stack Trace Analysis Walk the stack frame by frame, starting from the origin: - **
- Required Inputs
- Output Format
- 1. Error Classification
- 2. Stack Trace Analysis
- 3. Root Cause Assessment
- 4. Affected Code Path
- 5. Suggested Fix
- 6. Next Debugging Steps
- 7. Prevention
- Quality Checks
- Anti-Patterns
- Usage Examples
What does the debugging-log-analyser skill do?
Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace walkthrough, probable root cause with confidence level, affected code path, a concrete code-level fix suggestion, and ordered next debugging steps.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill debugging-log-analyser --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.