What problem does it solve? Python bugs that tracebacks and print statements cannot explain require interactive inspection of live state, and long-running or subprocess-based programs cannot be debugged with simple print debugging. This Skill provides recipes for local pdb sessions, pytest debugging, post-mortem analysis, and remote debugging of running processes 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 and post-mortem debugging: Drop into pdb on test failures with --pdb, handle xdist conflicts, and inspect exception frames after crashes. - Remote debugging: Attach to long-running processes, daemons, and subprocesses using debugpy's DAP protocol or remote-pdb over netcat. - Use Case: A gateway subprocess misbehaves in production-like conditions and cannot be restarted. Add a remote-pdb set_trace call in the suspect handler, trigger the code path, connect with nc, and inspect the live stack and locals. ## Quick Start Add breakpoint() at the suspect line in my Python file and walk me through inspecting variables when the pdb prompt appears.
