skills.rest
opensquilla
opensquillaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

stack-trace-python-probe

Generates Python-specific root-cause checks, pytest reproducers, and patch targets for tracebacks.

6.8k|540|Updated May 6, 2026
Search Tags:#stack trace#Python#exception handling#Debugging#Root Cause Analysis#PyTest
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-python-probe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-trace-python-probe
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/stack-trace-python-probe
Command: npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-python-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When investigating a Python stack trace, engineers need a consistent checklist of language-specific root-cause checks, a minimal reproducer, and concrete patch targets rather than ad-hoc debugging notes.

Core Features & Use Cases

  • Python Root-Cause Checks: Produces checks for exception contracts, missing-key or None handling, and import/module/package boundary issues.
  • Pytest Reproducer Guidance: Suggests minimal reproduction commands using pytest -k <symbol> or python -m pytest <path> shapes.
  • Defensive Patch Targets: Identifies guard clauses, TypedDict or pydantic schema validation, and exception wrapping targets, plus verification commands.
  • Use Case: As an internal helper invoked by a meta stack-trace investigator, it structures the Python-specific portion of a traceback investigation into a fixed LANGUAGE_PROBE output format.

Quick Start

Ask the agent to investigate a Python traceback and it will return structured checks, a pytest reproducer, patch targets, and verification commands.

Frequently Asked Questions about stack-trace-python-probe

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

FAQPage Schema
How do I reproduce a Python traceback with pytest?▼

Use targeted pytest commands such as pytest -k <symbol> to run a specific test or python -m pytest <path> to run a test file. A minimal python -c snippet can also reproduce the failure in isolation.

What root-cause checks should I run for a Python exception?▼

Check the exception contract, missing-key and None-handling paths, and import or module/package boundary issues. These checks cover the most common causes behind Python tracebacks.

How do I write a defensive patch for a Python bug?▼

Add guard clauses for invalid inputs, enforce structure with TypedDict or pydantic schema validation, and wrap exceptions with meaningful context. Verify the fix with a targeted pytest command or a syntax and import check.

Can I invoke this skill directly as a user?▼

No, it is marked as an internal helper with user-invocable set to false and model invocation disabled. It is designed to be called by the meta-stack-trace-investigator skill during traceback analysis.

Does this probe suggest destructive debugging commands?▼

No, the instructions explicitly prohibit recommending destructive commands. It only suggests safe verification steps like targeted pytest runs and Python syntax or import checks.

Related Skills

Explore More Software Engineering Skills→
Unique-AGUnique-AG
5

python-debug

Decode Python tracebacks and guide pdb debugging workflows.

Official
Intermediate
AlphaLab-USTCAlphaLab-USTC
131

run-tests

Run OhMyCode pytest suites and analyze failures with tracebacks.

Community
Intermediate
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
SethyPagnaSethyPagna

python-debugpy

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

Community
Advanced