python-debugging-expert

sandraschi's avatarfrom sandraschi

Master debugger for Python code with expertise in common errors, performance issues, and debugging tools

⭐3stars🔀1forks📁View on GitHub🕐Updated Dec 21, 2025

When & Why to Use This Skill

This Claude skill serves as a comprehensive Python debugging expert, designed to identify and resolve complex code errors, performance bottlenecks, and memory leaks. It leverages advanced diagnostic tools like pdb and debugpy, providing structured playbooks for triaging issues, stabilizing reproduction pipelines, and optimizing asynchronous and concurrent code for modern Python environments (including Python 3.13).

Use Cases

  • Case 1: Rapidly triaging and fixing runtime exceptions and logic errors in Python scripts using structured diagnostic templates and IDE-integrated debugging tools.
  • Case 2: Optimizing application performance by profiling CPU hotspots and identifying memory leaks or garbage collection issues in high-load systems.
  • Case 3: Troubleshooting complex concurrency issues, such as race conditions and deadlocks in asyncio or multiprocessing environments to ensure thread safety.
  • Case 4: Establishing reliable bug reproduction pipelines and automated test fixtures to prevent regression of previously resolved issues.
namepython-debugging-expert
descriptionMaster debugger for Python code with expertise in common errors, performance issues, and debugging tools
licenseProprietary

Python Debugging Expert

Status: ✅ Research complete Last validated: 2025-11-08 Confidence: 🟡 Medium — Research-backed debugging playbook – review semi-annually

How to use this skill

  1. Begin with modules/core-guidance.md to triage the issue and plan reproduction.
  2. Use modules/diagnostics-and-tooling.md to select appropriate debuggers and tracing tools.
  3. Resolve concurrency issues via modules/async-and-concurrency.md.
  4. Address hotspots and leaks with modules/performance-and-memory.md.
  5. Stabilize reproduction pipelines through modules/testing-and-reproduction.md.
  6. Track follow-ups in modules/known-gaps.md and revisit modules/research-checklist.md every six months.

Module overview

Research status

  • Updated for Python 3.13 debugging improvements, async task diagnostics, and modern tooling.
  • Next review due 2026-05-01 or sooner if CPython introduces major debugging changes.
  • Known gaps capture C extension debugging and distributed tracing coverage pending further work.