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() in source, launch scripts under python -m pdb, or drop into pdb on pytest failures with --pdb and --trace. - Remote debugging with debugpy: Attach to already-running processes via DAP on port 5678, using source-edit listeners, -m debugpy launch, or PID-based injection. - Post-mortem inspection: Catch exceptions and inspect locals at the crash site using pdb.post_mortem or a custom sys.excepthook. - Use Case: A Hermes gateway subprocess misbehaves in production. Add remote_pdb.set_trace() at the suspect handler, trigger it, connect with nc 127.0.0.1 4444, and inspect the live call stack and variables without restarting the service. ## Quick Start Add a breakpoint() call at the suspicious line in my Python file and show me how to inspect the variables when execution pauses there.
