skills.rest
Hieubkav
HieubkavCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-strategies

Apply a structured multi-phase debugging methodology to identify and resolve software defects.

Updated Feb 23, 2025
Search Tags:#templates#debugging#troubleshooting#checklists#root-cause#production-debugging
One-click install
npx skills add https://github.com/Hieubkav/Ph-ng-Kh-m-Ng-c-Nh-n --skill debugging-strategies-hieubkav
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-strategies
Source: https://github.com/Hieubkav/Ph-ng-Kh-m-Ng-c-Nh-n/tree/main/.claude/skills/debugging-strategies
Command: npx skills add https://github.com/Hieubkav/Ph-ng-Kh-m-Ng-c-Nh-n --skill debugging-strategies-hieubkav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It helps engineers make debugging systematic, reducing guesswork and accelerating root-cause analysis across diverse stacks and environments.

Core Features & Use Cases

  • Systematic debugging framework covering reproduction, information gathering, hypothesis formation, and verification.
  • Cross-language applicability across codebases, production systems, and performance issues.
  • Practical tooling guidance, templates, checklists, and code examples.
  • Helpful guidance for debugging flaky, memory, and production bugs with repeatable workflows.

Quick Start

Describe the issue you are facing, then apply the structured debugging framework to isolate and verify the root cause.

Frequently Asked Questions about debugging-strategies

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

FAQPage Schema
How do I systematically debug production bugs instead of guessing?▼

Systematic debugging of production bugs requires a structured methodology covering reproduction, information gathering, and hypothesis verification to pinpoint root causes efficiently and reduce guesswork.

What is the best way to troubleshoot unexpected code behavior across different programming languages?▼

Troubleshooting unexpected code behavior across languages requires a cross-environment debugging framework that applies repeatable workflows for information gathering and hypothesis testing to isolate and verify the root cause.

How do I find the root cause of flaky bugs and memory leaks?▼

Finding the root cause of flaky bugs and memory leaks requires structured workflows with reproducibility steps and practical tooling guidance to systematically isolate and verify defects in codebases.

Can I use a structured debugging methodology for performance issues in production systems?▼

Yes, the structured debugging methodology applies to performance issues in production systems through multi-phase information gathering, hypothesis formation, and verified fixes for resolving unexpected behavior.

What checklists and templates should I follow for root-cause analysis?▼

Root-cause analysis checklists and templates should guide you through reproduction, information gathering, hypothesis testing, and verified fixes to ensure systematic debugging and efficient defect resolution.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
StudentCristianStudentCristian

nw-bugfix

Coordinate root-cause analysis, user validation, and regression testing for defect resolution.

Community
Advanced
KrishnatejavepaKrishnatejavepa
14

observability-and-instrumentation

Instrument code with logging, metrics, tracing, and alerting for production observability.

Community
Advanced
CANTAGESTUDIOCANTAGESTUDIO
3

systematic-debugging

Diagnose software defects through a four-phase root-cause investigation framework.

Community
Advanced