skills.rest
LuizEduPP
LuizEduPPCOMMUNITY
Explore all skills by this author →
GitHub

debugging-strategies

Reproduce, diagnose, and resolve bugs using structured debugging workflows.

Updated Apr 10, 2026
Search Tags:#debugging#troubleshooting#logging#profiling#root-cause#bug-hunting#hypothesis-testing
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill debugging-strategies-luizedupp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-strategies
Source: https://github.com/LuizEduPP/skills/tree/main/debugging-strategies
Command: npx skills add https://github.com/LuizEduPP/skills --skill debugging-strategies-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill stops the guesswork during debugging by guiding you through a repeatable process to reproduce issues, gather diagnostics, form hypotheses, test fixes, and document findings so you can resolve bugs, performance regressions, and crashes reliably.

Core Features & Use Cases

  • Structured debugging phases walks you through reproduction, information gathering, hypothesis formation, and verification so you never skip a critical step.
  • Language-agnostic tooling highlights JavaScript, Python, and Go debugging snippets plus profiling, tracing, and logging techniques that work across stacks.
  • Advanced patterns cover intermittent problems, performance slowdowns, memory leaks, and production crashes, making it ideal for developers investigating tricky bugs or regressions.

Quick Start

Ask the assistant to apply the debugging strategies workflow to reproduce the issue and test hypotheses with targeted logging and profiling tools.

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 an intermittent bug in a complex codebase?▼

Systematic debugging of intermittent bugs requires structured reproduction, information gathering, and hypothesis testing. You walk through defined phases to reproduce the issue, gather diagnostics via logging, and verify fixes to resolve elusive crashes reliably.

What is the best way to troubleshoot memory leaks in production?▼

Troubleshooting memory leaks demands structured information gathering and profiling. You reproduce the production crash scenario, apply memory profiling tools, test targeted hypotheses, and document findings to resolve the leak without guesswork.

Can I use this debugging workflow with JavaScript, Python, and Go environments?▼

Yes, the debugging workflow supports JavaScript, Python, and Go environments. It provides language-agnostic tooling alongside specific debugging snippets, profiling techniques, and tracing tools that work across these stacks.

How do I stop guessing and find the root cause of a software bug?▼

Finding the root cause of a bug requires structured hypothesis testing instead of guessing. You reproduce the issue, gather diagnostics, form targeted hypotheses, test fixes systematically, and document findings to ensure reliable resolution.

Does systematic debugging help with distributed systems and production crashes?▼

Yes, systematic debugging is designed for distributed systems and production crashes. It guides you through reproducing elusive issues, applying tracing and logging tools, and verifying fixes to resolve complex regressions reliably.

Related Skills

Explore More Software Engineering Skills→
11547613341154761334

debug

Configure namespace-specific debug logging in JavaScript or TypeScript projects.

Community
Basic
mazicimertmazicimert

tdd-bug-fix

Reproduce bugs with failing tests and guide a minimal TDD fix workflow.

Community
Advanced
Adam-GuerinAdam-Guerin
1

performance-engineer

Diagnose application bottlenecks using observability, profiling, and load testing techniques.

Community
Advanced
vertivolatamvertivolatam
1

Error Tracking & Crash Reporting

Track Flutter crashes with Sentry and Firebase Crashlytics.

Official
Advanced