python-automated-debugging

Run automated non-interactive pdb sessions to collect runtime state from failing Python tests.

Updated Feb 11, 2018
One-click install
npx skills add https://github.com/tpott/pub_musings --skill python-automated-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-automated-debugging
Source: https://github.com/tpott/pub_musings/tree/main/cc_plugins/skills/python-automated-debugging
Command: npx skills add https://github.com/tpott/pub_musings --skill python-automated-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers diagnose failing Python tests by running automated, non-interactive pdb sessions to capture runtime state for analysis.

Core Features & Use Cases

  • Uses the debug_session tool to run deterministic pdb commands and collect structured output for debugging.
  • Enables iterative hypothesis testing by inspecting variables, stack frames, and program flow without manual step-by-step interaction.
  • Works on macOS and Linux environments with the included script in the skill directory to simplify debugging workflows.

Quick Start

Run python debug_session.py <script.py> with a predefined set of pdb commands to inspect runtime state and identify the bug.

Frequently Asked Questions about python-automated-debugging

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

FAQPage Schema
How do I automate Python debugging to inspect runtime state without stepping through manually?

You can automate Python debugging by running non-interactive pdb sessions with predefined command sequences to collect structured runtime state for analysis. This captures variables and stack frames without manual step-by-step interaction.

What is the best way to debug Python tests that keep failing after multiple attempts?

The best way to debug persistently failing Python tests is running automated pdb sessions to trace variable values across calls. This collects deterministic runtime state to reveal issues that print debugging misses.

Can I run automated pdb sessions to capture stack frames on macOS and Linux?

Yes, you can run automated pdb sessions on macOS and Linux environments. The skill includes scripts in its directory that execute deterministic command sequences to capture stack frames and program flow.

How do I run pdb commands non-interactively to trace variable values across calls?

You run pdb commands non-interactively by executing the debug_session.py script with your target script. Provide a predefined set of pdb commands to inspect runtime state and identify the bug automatically.

When should I use automated pdb sessions instead of print debugging?

You should use automated pdb sessions when print debugging is not revealing the issue, when a test has failed multiple times, or when tracing variable values across calls is necessary to identify the bug.