debugging

Diagnose runtime errors, performance bottlenecks, and logic flaws across Python, JavaScript/TypeScript, Go, and JVM.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xxipv6/claudeSandBox --skill debugging-xxipv6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/xxipv6/claudeSandBox/tree/main/claudeCode-none/claude_arm64/workspace/.claude/skills/debugging
Command: npx skills add https://github.com/xxipv6/claudeSandBox --skill debugging-xxipv6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

系统化调试方法论、工具使用、问题定位和解决技巧。当代码行为不符合预期、出现错误需要诊断或性能问题需要分析时,应主动(PROACTIVELY)使用此 skill。

Core Features & Use Cases

  • 科学调试法(Scientific Debugging)是一个实用的分步流程,覆盖观察、假设、实验、验证、修复等阶段,帮助定位根因并快速验证解决方案。
  • 支持多语言环境的调试流程模板和清单,适用于 Python、JavaScript/TypeScript、Go 等语言的运行时错误、性能瓶颈和逻辑缺陷的诊断。
  • 提供系统化的调试工具使用示例(pdb/ipdb、Chrome DevTools、Delve、JDB 等)以及性能分析与日志最佳实践,帮助提升排错效率。

Quick Start

Describe the issue and provide relevant logs to start the debugging session.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is the systematic debugging method for diagnosing runtime errors in Python and JavaScript?

Systematic debugging enforces a structured workflow of Observe, Hypothesize, Experiment, Verify, and Fix to diagnose runtime errors and logic flaws across Python, JavaScript/TypeScript, Go, and JVM environments.

How do I find performance bottlenecks using debugging tools like pdb and Chrome DevTools?

To find performance bottlenecks, apply systematic debugging tool usage guidance for pdb, ipdb, Chrome DevTools, and Delve, leveraging performance analysis and logging best practices to identify root causes efficiently.

Can I use this systematic debugging workflow for Go and JVM projects?

Yes, the systematic debugging workflow applies to Go and JVM projects, providing structured templates and checklists for diagnosing runtime errors, performance bottlenecks, and logic defects across these language environments.

What's the best way to triage software issues when code behavior doesn't match expectations?

The best way to triage software issues is applying scientific debugging methodologies, starting by describing the issue and providing relevant logs to initiate the structured observation and hypothesis workflow.

How to fix logic flaws by applying a scientific debugging methodology step by step?

Fix logic flaws by progressing through the scientific debugging steps: Observe the defect, Hypothesize the cause, Experiment with tool usage, Verify the results, and apply the Fix, using provided checklists to ensure accuracy.