python-debugger

Analyze Python tracebacks to identify root causes and propose fixes.

6|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/archibate/archibate-skills --skill python-debugger-archibate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-debugger
Source: https://github.com/archibate/archibate-skills/tree/main/old-skills/redundant-skills/python-debugger
Command: npx skills add https://github.com/archibate/archibate-skills --skill python-debugger-archibate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quickly interpret Python tracebacks and runtime failures to find the root cause, produce a minimal reproduction, and provide targeted fixes so developers can restore correct behavior with confidence.

Core Features & Use Cases

  • Traceback analysis: Read and explain stack traces, identify the exact failing line and call chain.
  • Reproduction & isolation: Guide creation of minimal test cases that reliably reproduce errors.
  • Root cause patterns: Diagnose common causes such as None values, type mismatches, mutable defaults, circular imports, async/await mistakes, and encoding issues.
  • Fix recommendations & verification: Propose defensive fixes, logging and profiling strategies, and pytest tests to verify the resolution.
  • Tools & workflows: Explain using pdb, icecream, rich tracebacks, logging configuration, cProfile, and memory profiler for deeper investigation.

Quick Start

Ask the skill to analyze the provided traceback, produce a minimal reproducible test case, identify the root cause, and propose a code patch plus a pytest to verify the fix.

Frequently Asked Questions about python-debugger

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

FAQPage Schema
How do I analyze a Python traceback to find the root cause?

To analyze a Python traceback, you read the stack trace to identify the exact failing line and call chain, then isolate common root causes like None values or type mismatches to propose targeted fixes.

Can I get pytest-based verification guidance for a Python logic bug fix?

Yes, you can receive pytest-based verification guidance that proposes defensive code changes alongside a minimal test case to reliably reproduce the error and confirm the resolution.

How do I debug async/await issues and circular imports in Python?

Debug async/await issues and circular imports by examining the traceback call chain to identify the specific module loading or coroutine execution failure, then applying structural code changes.

Does this approach work with pdb and cProfile for runtime error profiling?

Yes, this approach works with pdb and cProfile by explaining how to utilize these tools, alongside icecream and memory profiler, for deeper investigation of runtime errors and logic bugs.

What are common root cause patterns for ZeroDivisionError and type mismatches in Python?

Common root cause patterns for ZeroDivisionError and type mismatches include unexpected None values, mutable defaults, and encoding issues, which are identified by analyzing the exception traceback.