skills.rest
MusserLab
MusserLabOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debugging-before-patching

Diagnose errors and document root causes before proposing fixes.

2|Updated Feb 18, 2026
Search Tags:#debugging#diagnostics#best-practices#reproducibility#bug-fixing#error-diagnosis#trace-data-flow
One-click install
npx skills add https://github.com/MusserLab/lab-claude-skills --skill debugging-before-patching
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-before-patching
Source: https://github.com/MusserLab/lab-claude-skills/tree/main/skills/debugging-before-patching
Command: npx skills add https://github.com/MusserLab/lab-claude-skills --skill debugging-before-patching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When something doesn't work or the user reports an error, diagnose first — never jump straight to writing fixes.

Core Features & Use Cases

  • Diagnose errors before patching and write diagnostic steps to uncover root causes.
  • Share findings with the user and guide corrective actions based on evidence.
  • Propose fixes only after validating the root cause and confirming reconstruction of the issue.

Quick Start

Diagnose a reported issue by first reproducing it, tracing the failing step, and documenting findings before proposing any fix.

Frequently Asked Questions about debugging-before-patching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why should I diagnose errors before patching code during a debugging session?▼

Diagnosing errors before patching code ensures you uncover the actual root cause. Jumping straight to writing fixes risks treating symptoms, while deterministic diagnostic steps validate the issue and guide evidence-based corrective actions.

How do I find a root cause before writing a bug fix?▼

Reproduce the reported issue, trace the failing step in the data flow, and document your findings. Propose fixes only after validating the root cause and confirming you can reconstruct the issue.

Can I use this diagnostic approach for data pipeline failures and user-reported bugs?▼

Yes, this approach applies to debugging data pipelines, user-reported failures, and software workflows. It enforces non-destructive analysis to investigate unhealthy behavior across diverse development environments.

What is the best way to trace data flow when diagnosing an error?▼

The best way to trace data flow is through non-destructive analysis. Enforce deterministic diagnostic steps to track failing operations, ensuring you share findings and guide corrective actions based on evidence.

When should I not jump straight to writing code fixes?▼

You should never jump straight to writing fixes when an error is reported. Skip patching until you have reproduced the issue, traced the failing step, and confirmed reconstruction of the problem.

Does non-destructive analysis guarantee finding the root cause of a bug?▼

Non-destructive analysis enforces deterministic diagnostic steps to uncover root causes, but it requires you to trace the failing step and validate findings. You propose fixes only after confirming issue reconstruction.

Related Skills

Explore More Software Engineering Skills→
majedsiefalnasrmajedsiefalnasr

gitnexus-debugging

Trace bugs in a knowledge graph-enabled codebase to identify error origins and affected components.

Community
Advanced
rittmananalyticsrittmananalytics
8

dbt-troubleshooting

Classifies Airflow errors and guides users through step-by-step troubleshooting and recovery workflows.

Official
Advanced
sigitpoerwosigitpoerwo

fix-errors

Trace unhandled errors from telemetry dashboards to their data producers.

Community
Advanced
DangQuangSEDangQuangSE
19

ck:fix

Diagnose, fix, and review software bugs from error messages or test reports.

Community
Advanced