What problem does it solve? Python bugs in tests, long-running daemons, and subprocesses are hard to diagnose from tracebacks alone, and attaching a debugger to an already-running process is often confusing. This Skill provides concrete recipes for interactive debugging with pdb, post-mortem analysis, and remote debugging via debugpy or remote-pdb. ## Core Features & Use Cases - Local pdb debugging: Insert breakpoint() calls, launch scripts under python -m pdb, and use the full pdb command set (step, breakpoints, stack navigation, interact mode). - Pytest integration: Drop into pdb on test failure with --pdb, including the required -p no:xdist workaround for pytest-xdist. - Remote and post-mortem debugging: Attach debugpy to running processes via DAP, inject into a PID, or use remote-pdb over netcat for terminal-friendly sessions; run post-mortem inspection on uncaught exceptions. - Use Case: A gateway subprocess misbehaves in production and cannot be restarted. Add a remote-pdb set_trace call in the suspect handler, trigger the code path, connect with nc 127.0.0.1 4444, and inspect locals and the call stack live. ## Quick Start Add breakpoint() at the suspect line in my Python file and walk me through using pdb commands to inspect the variables when it pauses.
