debugging-log-analyser
The debugging-log-analyser Claude Code skill systematically parses error logs, stack traces, and crash reports into a structured root cause diagnosis. Use this skill when applications throw exceptions, crash unexpectedly, or produce errors and you need to identify the underlying issue and resolution path. It delivers error classification, frame-by-frame stack trace analysis, probable root cause with confidence assessment, affected code paths, concrete code-level fix suggestions, and prioritized next debugging steps.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/debugging-log-analyser && cp -r /tmp/debugging-log-analyser/plugins/pm-engineering/skills/debugging-log-analyser ~/.claude/skills/debugging-log-analyserSKILL.md
# 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: - **Origin frame:** [File, line, function where it started] - **Propagation path:** [How it travelled through the call stack] - **Crash point:** [Where it ultimately threw/panicked/exited] For each significant frame, note whether it is: - User code (fixable here) - Framework/library code (usually a misuse issue) - System/runtime code (usually a config or environment issue) ### 3. Root Cause Assessment **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] ### 4. Affected Code Path **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] ### 5. Suggested Fix Provide a concrete, code-level suggestion: - What to change (the minimal fix) - Why this fixes the root cause - Any trade-offs or risks in the fix - A short code snippet if helpful ### 6. Next Debugging Steps If the root cause is uncertain, provide an ordered list of 3–5 specific debugging actions: 1. [Specific thing to check — file, log line, config value] 2. [Specific reproduction step or isolation test] 3. [Specific tool command — e.g. `strace`, `pprof`, `--verbose`, add logging at X] ### 7. Prevention One or two concrete things that would prevent this class of error recurring: - Better input validation at [point] - Add monitoring/alerting for [condition] - Test that covers [scenario] --- ## Quality Checks - [ ] Root cause is specific (not "there might be a null pointer issue") - [ ] At least one concrete code-level fix is suggested - [ ] Next steps are actionable commands, not vague advice - [ ] Suggested fix references the actual language/framework in the input (not a generic fix that could apply to any language) - [ ] Confidence level includes a stated reason (not just "High" or "Low" with no explanation) - [ ] Prevention is proactive (not just "add error handling") ## Usage Examples - "Why is this crashing?" + [paste log] - "Can you analyse this stack trace?" - "I'm getting this error, what does it mean?" - "Debug this log for me" - "What's causing this exception?"
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.