skills.rest
Kuass
KuassCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide four-phase debugging with root cause investigation before fixes.

1|Updated Mar 4, 2026
Search Tags:#testing#debugging#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/Kuass/kiro-gateway-plus --skill systematic-debugging-kuass
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Kuass/kiro-gateway-plus/tree/main/.opencode/skill/systematic-debugging
Command: npx skills add https://github.com/Kuass/kiro-gateway-plus --skill systematic-debugging-kuass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of inefficient and ineffective debugging by providing a structured, four-phase framework to ensure root cause analysis before any fixes are attempted, preventing wasted time and the introduction of new bugs.

Core Features & Use Cases

  • Structured Debugging Process: Guides users through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
  • Evidence-Based Approach: Emphasizes gathering data and forming hypotheses based on observable evidence rather than guesswork.
  • Use Case: When a critical test fails in a CI/CD pipeline, this Skill ensures the developer systematically investigates the error messages, reproduces the failure, analyzes recent code changes, and forms a testable hypothesis before proposing a solution, leading to a faster and more reliable fix.

Quick Start

Use the systematic-debugging skill to investigate a test failure in the CI pipeline.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging process for finding the root cause of a bug?▼

Systematic debugging is a four-phase framework mandating root cause investigation before fixes. It guides developers through evidence gathering, pattern analysis, and scientific hypothesis testing to resolve issues without introducing new bugs.

How do I debug a failing test in a CI/CD pipeline?▼

To debug a failing test, you systematically investigate error messages, reproduce the failure, analyze recent code changes, and form a testable hypothesis before proposing a solution, leading to a faster and more reliable fix.

How do I troubleshoot performance problems without guessing the fix?▼

You troubleshoot performance problems using an evidence-based approach that emphasizes gathering data and forming hypotheses based on observable evidence rather than guesswork, ensuring you test assumptions scientifically before implementing changes.

Can I integrate root cause tracing with test-driven development?▼

Yes, the systematic debugging framework integrates with root-cause-tracing and test-driven-development skills. This combination provides comprehensive issue resolution by linking hypothesis testing directly to test validation.

What's the best way to fix software bugs without introducing new issues?▼

The best way to fix software bugs safely is to mandate root cause investigation before attempting any fixes, preventing wasted time and avoiding the introduction of new bugs through structured pattern analysis and hypothesis testing.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
pcaokhaipcaokhai

investigate

Trace software bugs to root causes through a structured multi-phase investigation workflow.

Community
Advanced
maxjuniorbrmaxjuniorbr
2

systematic-debugging

Guide root-cause debugging through a four-phase investigation workflow.

Community
Advanced
yocxy2yocxy2

gstack-openclaw-investigate

Trace software symptoms to architectural root causes via a five-phase diagnostic workflow.

Community
Advanced