What problem does it solve? Diagnosing why Python code fails is hard when tracebacks alone don't reveal wrong values, and long-running processes like gateways or daemons can't simply be restarted to add print statements. This Skill provides structured recipes for interactive debugging with pdb and remote debugging with debugpy. ## Core Features & Use Cases - Local pdb debugging: Insert breakpoint() for an interactive REPL, launch scripts under python -m pdb, or trap pytest failures with --pdb and --trace. - Post-mortem inspection: Catch exceptions and inspect locals at the crash site using pdb.post_mortem or a custom sys.excepthook. - Remote debugging with debugpy: Attach to already-running processes via DAP on port 5678, with patterns for source-edit listen, -m debugpy launch, and PID injection. - Use Case: A gateway subprocess misbehaves in production-like conditions. Add remote_pdb.set_trace() in the suspect handler, trigger it, then connect with nc 127.0.0.1 4444 to inspect the suspended frame and pending asyncio tasks. ## Quick Start Ask the agent to add a breakpoint in the failing Python function and walk you through inspecting the local variables when it hits.
