skills.rest
kaivyy
kaivyyCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose software bugs through a four-phase root cause analysis methodology.

20|7|Updated Feb 11, 2026
Search Tags:#testing#debugging#investigation#root cause#troubleshooting#bug fixing
One-click install
npx skills add https://github.com/kaivyy/kabot --skill systematic-debugging-kaivyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/kaivyy/kabot/tree/main/kabot/skills/systematic-debugging
Command: npx skills add https://github.com/kaivyy/kabot --skill systematic-debugging-kaivyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust, step-by-step framework to systematically diagnose and resolve bugs, test failures, and unexpected behavior, ensuring that the root cause is identified and fixed, rather than just addressing superficial symptoms.

Core Features & Use Cases

  • Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue before applying any fixes.
  • Pressure Resistance: Includes rules and language designed to prevent shortcuts under time pressure or when a quick fix seems obvious.
  • Use Case: When a critical test fails in CI, this skill ensures the engineer doesn't just add a temporary workaround but thoroughly investigates to prevent recurrence.

Quick Start

Use the systematic debugging skill when encountering any bug or unexpected behavior to ensure root cause analysis.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a bug instead of just fixing symptoms?▼

A systematic debugging approach enforces root cause analysis through a four-phase process: investigation, pattern analysis, hypothesis testing, and implementation, explicitly overriding rationalizations to take shortcuts under time pressure.

How do I debug failing CI tests without applying temporary workarounds?▼

Debug failing CI tests by following a structured methodology that mandates thorough investigation and hypothesis testing to identify the root cause, ensuring permanent bug resolution rather than temporary workarounds.

How does a systematic debugging methodology handle time pressure during bug fixing?▼

Systematic debugging handles time pressure by embedding specific rules and language that resist the urge to apply obvious quick fixes, forcing engineers to complete full root cause analysis before implementation.

When should I use a structured troubleshooting process for software investigation?▼

Use a structured troubleshooting process whenever encountering unexpected behavior, test failures, or bugs to ensure pattern identification and hypothesis testing are completed before applying any code changes.

Can this root cause investigation methodology be applied to any software development bug resolution?▼

Yes, this root cause investigation methodology is applicable to all software development bug resolution scenarios, providing a universal framework for diagnosing and fixing unexpected technical issues.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
StudentCristianStudentCristian

nw-bugfix

Coordinate root-cause analysis, user validation, and regression testing for defect resolution.

Community
Advanced
aporto-techaporto-tech

Qa Only

Generate QA reports with health scores and screenshots for web applications.

Official
Advanced
KakarottooooKakarottoooo

investigate

Identify and isolate root causes of bugs through a structured four-phase investigation workflow.

Community
Advanced