skills.rest
mikeparcewski
mikeparcewskiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging

Apply a six-step debugging process to diagnose errors and root causes.

8|2|Updated Feb 9, 2026
Search Tags:#performance#debugging#troubleshooting#root-cause#systems#problem-diagnosis
One-click install
npx skills add https://github.com/mikeparcewski/wicked-garden --skill debugging-mikeparcewski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/engineering/debugging
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill debugging-mikeparcewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging and root-cause analysis for investigating errors, diagnosing complex issues, and performance profiling.

Core Features & Use Cases

  • Six-step debugging process: understand the problem, gather evidence, form and test hypotheses, implement fixes, and document learnings.
  • Structured evidence collection, log and trace analysis, and pattern recognition to identify root causes.
  • Integration discovery patterns and risk assessment templates to evaluate external dependencies.
  • Templates and checklists for consistent investigations, severity assessment, and regression planning.
  • Real-world use cases include diagnosing intermittent failures, tracing production incident root causes, and validating fixes before deployment.

Quick Start

Describe the issue you want to investigate, and I will initiate a structured debugging workflow.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is structured root-cause analysis for software debugging?▼

Structured root-cause analysis is a systematic debugging method that investigates errors through evidence collection, hypothesis testing, and pattern recognition to identify the exact origin of software issues. It replaces guesswork with a repeatable six-step diagnostic process.

How do I debug intermittent production failures and trace their root cause?▼

Debug intermittent production failures by gathering logs and traces, forming hypotheses based on evidence templates, and testing each hypothesis systematically. This structured approach isolates variables to trace the exact root cause of the failure.

What is the best way to diagnose performance bottlenecks across a codebase?▼

The best way to diagnose performance bottlenecks is applying a structured debugging workflow that profiles the codebase, collects evidence, and tests hypotheses. This method ensures you identify the true bottleneck rather than treating symptoms.

Can I use this structured debugging process for integration failures in deployments?▼

Yes, you can use this structured debugging process for integration failures. It includes integration discovery patterns and risk assessment templates to evaluate external dependencies and diagnose failures across deployments systematically.

How do I document debugging learnings and plan for regression after a fix?▼

Document debugging learnings and plan for regression by using the final steps of the debugging process, which provide templates for documenting investigations, assessing severity, and creating regression plans to validate fixes before deployment.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
mandersogitmandersogit

debugging

Debug Python code by reproducing issues, analyzing logs, and verifying fixes.

Community
Basic
pessinamisticpessinamistic
1

debugging

Reproduce software defects and trace correlation IDs across microservice logs.

Community
Advanced
StrategicMilkStrategicMilk

Monitoring and Alerting

Detect operational anomalies in system metrics using statistical process control.

Community
Advanced