python-debugpy

Attach interactive debuggers to Python processes for breakpoint-driven tracing.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill python-debugpy-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-debugpy
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/software-development/python-debugpy
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill python-debugpy-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect Python failures when logging is not enough, whether you need to stop at a precise line, replay a failing test, or attach to a process that is already running.

Core Features & Use Cases

  • Local breakpoint debugging: Pause execution with breakpoint and inspect variables directly in pdb.
  • Script and test tracing: Run scripts or pytest cases under pdb to step through failures without changing application logic.
  • Remote and post-mortem debugging: Attach to long-lived services with debugpy or trap crashes after exceptions, including desktop backends, gateways, and subprocesses.
  • Use Case: A Python service behaves differently in production than in your editor, and this Skill lets you attach, set breakpoints, and inspect the exact call stack and locals.

Quick Start

Use the python-debugpy skill to attach to the failing Python process and step through the code path where the error occurs.

Frequently Asked Questions about python-debugpy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Python service that is already running in production?

You can debug a running Python service by using debugpy to remotely attach to the live process. This allows you to set breakpoints, inspect the exact call stack, and examine local variables without altering application logic.

How do I step through a failing pytest case with pdb?

Run pytest cases under pdb to step through failures directly. This pauses execution at the exact error point, enabling interactive stack inspection and variable tracing without changing the test logic.

What is post-mortem debugging in Python and when do I need it?

Post-mortem debugging traps crashes after exceptions occur, allowing you to inspect the program state at the failure point. It is needed when you must analyze the exact call stack and local variables after a process has crashed.

Can I attach a debugger to Python child processes and subprocesses?

Yes, you can attach debuggy to Python child processes and subprocesses. It supports breakpoint-driven tracing and stack inspection across spawned processes, including desktop backends and gateways.

Does this debugging approach work with DAP-compatible editors?

Yes, remote attach support works through DAP-compatible debugging workflows. This enables you to connect your editor to local scripts or long-running services for interactive tracing.

Why use an interactive debugger instead of adding print statements to Python scripts?

Interactive debugging pauses execution at precise lines to inspect variables directly, which is faster than logging. It captures exact call stacks and local states during runtime failures where print statements fall short.