skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate Qwen bugs and test failures through structured root-cause phases.

Updated May 11, 2026
Search Tags:#debugging#troubleshooting#qa#root-cause-analysis#system-diagnostics
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill systematic-debugging-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/qwen_skills/systematic-debugging
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill systematic-debugging-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging addresses the tendency to apply quick, symptom-based fixes and instead enforces a structured process to identify the root cause of bugs, test failures, and unexpected behavior before attempting any fix.

Core Features & Use Cases

  • Four-phase discipline: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation with verification.
  • Reproducibility and evidence gathering are mandatory before changes.
  • Applicable to any technical issue in Qwen, including errors, performance problems, and integration issues across components.

Quick Start

Begin by documenting the observed issue, reproduce it consistently, and apply Phase 1 procedures to uncover the root cause.

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 bugs instead of applying quick fixes?▼

Root-cause debugging enforces a structured four-phase process—investigation, pattern analysis, hypothesis testing, and implementation—requiring evidence and reproducibility checks before proposing any fixes.

What is the best way to troubleshoot integration issues across components in Qwen?▼

Systematic debugging applies root-cause investigation to any technical issue in Qwen, analyzing errors and integration challenges across components using structured pattern analysis before changes.

How do I investigate test failures using a structured debugging approach?▼

Investigate test failures by reproducing the issue consistently, analyzing patterns in the observed behavior, testing hypotheses with evidence, and verifying fixes during implementation.

Can I use systematic debugging for performance problems, or is it only for code errors?▼

Yes, this root-cause debugging approach is applicable to any technical issue in Qwen, including performance problems, unexpected behavior, and integration challenges across components.

Why does my debugging process lack reproducibility checks before code changes?▼

Structured system diagnostics mandate reproducibility and evidence gathering before implementation, ensuring that pattern analysis and hypothesis testing validate the root cause prior to fixes.

When should I not use a symptom-based troubleshooting approach for system diagnostics?▼

Avoid symptom-based troubleshooting when dealing with complex Qwen integration challenges or persistent test failures, as structured root-cause analysis with hypothesis testing is necessary for effective fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
linenoizelinenoize
1

fix

Apply diagnosed code changes and verify repairs with tests.

Community
Advanced
samjhechtsamjhecht
4

systematic-debugging

Diagnose root causes of bugs using a four-phase investigation workflow.

Community
Basic
ninjasitmninjasitm
2

systematic_debugging

Identify root causes before applying fixes in software debugging.

Community
Advanced