Capture error output, classify failure types, and trace root-cause hypotheses into a structured debug report.
npx skills add https://github.com/sqfzy/my_configs --skill debug-sqfzy
Please help me install this Agent Skill. Skill: debug Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/debug Command: npx skills add https://github.com/sqfzy/my_configs --skill debug-sqfzy
This tool provides a standalone root-cause tracer that captures an error, classifies it, traces the root cause, verifies hypotheses, and outputs a structured debug report. It does not implement fixes, tests, or commits. Use it to understand WHY something is broken before deciding how to fix it. Trigger when you want root-cause analysis only, such as when a user pastes an error and asks what causes it, or when you want to trace or diagnose a bug without fixing it. Do not trigger when you want the bug actually fixed (use /fix), you want to add tests (use /test), you are designing new features (use /design), or you want a design-level discussion (use /discuss).
Paste an error log or provide a path to a log file and run the tracer to generate a root-cause report.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis for software failures involves capturing error output, classifying the error type, and tracing causal paths. This process generates 1–3 plausible root-cause hypotheses supported by evidence before any fixes are implemented.
Yes, non-destructive root-cause tracing allows you to diagnose bugs without modifying your codebase. It preserves the original code and outputs a structured debug report with artifacts for review.
The best way to analyze why a specific module is failing is to run a standalone root-cause tracer targeting that file or module. It captures the error, traces causal paths, and presents plausible hypotheses with supporting evidence.
Yes, root-cause tracing can include automatic build and test execution to verify hypotheses. This helps understand why something is broken before implementing fixes, without actually modifying the codebase.
Use a root-cause tracer when you need to understand why something is broken before deciding how to fix it. Avoid using it when you want the bug actually fixed, tests added, or new features designed.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
pcaokhaiTrace software bugs to root causes through a structured multi-phase investigation workflow.
chrysaliscatGuide systematic debugging with debuggers, internet search agents, and codebase investigators.
poshan0126Diagnose bugs by parsing error logs and stack traces.
