What problem does it solve? Python bugs involving hidden locals, confusing state mutation, failing tests, subprocesses, or long-running services are hard to diagnose with print statements alone. This Skill guides interactive debugging so you can stop at the exact bad frame and inspect real program state. ## Core Features & Use Cases - Debugger Selection: Chooses the smallest tool for the job, from breakpoint() for local code to python3 -m pdb for no-edit launches and debugpy for remote or headless processes. - Remote and PID Attach: Starts debugpy listeners on 127.0.0.1, waits for DAP clients, or attaches to an already-running process by PID. - Post-Mortem Inspection: Captures tracebacks with pdb.post_mortem so unhandled exceptions can be examined after failure. - Use Case: A test suite fails only inside a worker pool. Disable parallel workers, run python3 -m pdb -c continue on the failing test, and inspect the exact frame where state diverges. ## Quick Start Ask the assistant to debug your failing Python script with pdb or attach debugpy to the running process so you can inspect variables at the point of failure.
