systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: woodfishhhh

Generate probability-ranked root causes with validation steps for repeated EZ_math_model failures.

32|1|Updated May 19, 2026

Search Tags:#debugging #root cause analysis #python packaging #workflow recovery #error traceback #validation steps #probability-ranked fixes

Ready to run

npx skills add https://github.com/woodfishhhh/EZ_math_model --skill systematic-debugging-woodfishhhh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/woodfishhhh/EZ_math_model/tree/main/skills/ez-math-model/tools/systematic-debugging
Command: npx skills add https://github.com/woodfishhhh/EZ_math_model --skill systematic-debugging-woodfishhhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stop wasting time on blind retries by turning repeated coder/packaging failures into structured root-cause hypotheses and validation steps.

Core Features & Use Cases

Root-cause oriented debugging: Generates 5–10 likely root causes when the same error repeats, rather than suggesting another generic attempt.
Validation-backed investigation: Each root cause comes with concrete verification steps so you can prove or rule out hypotheses.
Probabilistic repair guidance: Produces repair suggestions ordered by likelihood to guide the next action efficiently.

Quick Start

Load systematic-debugging and provide the failing code, full traceback, the relevant modeling_plan.md section, a preview of the attachment data, and what fixes have already been tried.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of recurring Python packaging failures and tracebacks?▼

Root cause analysis for recurring packaging failures identifies the most likely triggers from repeated exceptions and generates probability-ranked fixes. It uses the full traceback and prior repair attempts to produce structured corrective actions.

What is the best way to debug a model code execution that repeatedly throws the same exception?▼

Debugging recurring model code execution errors involves generating 5 to 10 likely root causes instead of blind retries. Each root cause hypothesis includes concrete validation steps to verify or rule out the specific failure trigger.

Why does my workflow recovery keep failing after attempting the same code fixes repeatedly?▼

Workflow recovery fails repeatedly when generic fixes do not address the underlying root cause. Systematic debugging turns repeated coder failures into structured hypotheses with explicit validation steps to prove or rule out each potential trigger.

How do I validate root cause hypotheses during error traceback analysis?▼

Validating root cause hypotheses during traceback analysis requires concrete verification steps for each potential trigger. This approach generates repair suggestions ordered by likelihood, guiding you to prove or rule out causes efficiently.

What information do I need to provide for effective root cause analysis of a failing coder run?▼

Effective root cause analysis requires the failing code, the full traceback, the relevant modeling plan section, a preview of attachment data, and a list of prior repair attempts. These inputs generate probability-ranked corrective actions.