skills.rest
ccf
ccfCOMMUNITY
Explore all skills by this author →
𝕏@cfigueirGitHub

debugging-strategies

Apply a structured debugging framework to reproduce, diagnose, and verify software defects.

1|Updated Dec 23, 2025
Search Tags:#debugging#methodology#profiling#trace#root-cause#reproduction#log-analysis
One-click install
npx skills add https://github.com/ccf/claude-code-ccf-marketplace --skill debugging-strategies-ccf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-strategies
Source: https://github.com/ccf/claude-code-ccf-marketplace/tree/main/plugins/developer-essentials/skills/debugging-strategies
Command: npx skills add https://github.com/ccf/claude-code-ccf-marketplace --skill debugging-strategies-ccf

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms debugging from frustrating guesswork into a repeatable, methodical process. It provides a structured framework, practical tools, and proven habits to locate root causes quickly across any codebase or technology stack.

Core Features & Use Cases

  • Phase-driven workflow: Reproduce, Gather Information, Form Hypothesis, Test & Verify to isolate issues efficiently.
  • Cross-language applicability: Useful for JavaScript/TypeScript, Python, Go, and other stacks with language-specific tips.
  • Advanced techniques library: Binary search debugging, differential debugging, trace debugging, and memory-leak detection.
  • Production debugging mindset: Safe investigation practices, logging-guided diagnosis, and verifiable fixes in real systems.

Quick Start

  1. Reproduce the issue with exact steps and a minimal workspace.
  2. Collect evidence: error messages, full stack traces, environment details, and recent changes.
  3. Form and test hypotheses by isolating components and varying inputs.
  4. Implement a fix and verify by re-running the reproduction and measuring impact.

Frequently Asked Questions about debugging-strategies

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

FAQPage Schema
What is the best way to systematically debug software defects across different languages?▼

Systematic debugging applies a structured framework to isolate issues across any stack. You reproduce the issue, gather evidence like stack traces, form hypotheses, and test fixes to ensure verifiable root-cause analysis.

How do I reproduce a production bug safely for root-cause analysis?▼

Reproduce production bugs by defining exact steps in a minimal workspace. Collect evidence such as error messages, environment details, and recent changes to form and test hypotheses without disrupting real systems.

What debugging techniques work for isolating hard-to-find memory leaks?▼

Memory-leak detection and trace debugging isolate issues by varying inputs and narrowing code paths. Binary search and differential debugging further cut the guesswork to verify root causes efficiently.

Can I use this structured debugging methodology for JavaScript and Python codebases?▼

Yes, the debugging methodology applies cross-language to JavaScript, TypeScript, Python, and Go. It provides language-specific tips to gather evidence, test hypotheses, and optimize performance across different environments.

Why does my debugging process fail to find the actual root cause of errors?▼

Debugging fails without deterministic reproduction and evidence collection. Forming hypotheses from full stack traces and recent changes, then verifying fixes by re-running reproduction steps, ensures accurate root-cause analysis.

Related Skills

Explore More Software Engineering Skills→
AndyAnh174AndyAnh174

debugger

Identify root causes of errors and test failures from messages and stack traces.

Community
Advanced
mscipiomscipio

systematic-debugging

Guide root cause analysis through hypothesis testing and verified implementation.

Community
Advanced
p-o-ke-naep-o-ke-nae

debugging-strategies

Isolate root causes of software bugs through evidence gathering and hypothesis testing.

Community
Advanced
kofttlcckofttlcc
14

systematic-debugging

Diagnose software defects through root cause analysis before code modification.

Community
Advanced