skills.rest
adrozdenko
adrozdenkoCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide AI agents through structured multi-phase debugging to identify root causes.

6|3|Updated Feb 24, 2026
Search Tags:#debugging#troubleshooting#software development#root cause analysis#bug fixing#knowledge capture
One-click install
npx skills add https://github.com/adrozdenko/soleri --skill systematic-debugging-adrozdenko
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/adrozdenko/soleri/tree/main/agents/salvador-filetree/skills/systematic-debugging
Command: npx skills add https://github.com/adrozdenko/soleri --skill systematic-debugging-adrozdenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time and new bugs caused by quick fixes or guessing, ensuring that the root cause of any technical issue is identified before any solution is attempted.

Core Features & Use Cases

  • Mandatory Root Cause Analysis: Enforces a strict process to find the origin of a bug before proposing fixes.
  • Phased Debugging: Guides through systematic investigation, pattern analysis, hypothesis testing, and implementation.
  • Knowledge Capture: Ensures that resolved issues and their solutions are documented to improve future debugging.
  • Use Case: When a critical test fails in production, this Skill ensures the AI doesn't just randomly change code but follows a structured approach to pinpoint the exact faulty logic and then captures that learning.

Quick Start

Use the systematic-debugging skill to debug the current test failure.

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 a software bug before attempting a fix?▼

Root cause analysis for software bugs requires a structured debugging process that searches existing knowledge bases, investigates systematically, and tests hypotheses before implementing fixes. This prevents superficial patches and ensures long-term system stability.

Why does quick fixing code lead to more bugs in production?▼

Quick fixing code without root cause analysis often introduces new bugs because it addresses symptoms rather than the faulty logic. Skipping structured troubleshooting and hypothesis testing risks destabilizing the system further.

What is the best way to debug a critical test failure without randomly changing code?▼

Debugging a critical test failure without random changes involves a multi-phase process: searching knowledge bases, investigating the issue, analyzing patterns, testing hypotheses, and capturing the solution. This systematic approach pinpoints exact faulty logic.

Can I capture and document resolved bug fixes to improve future troubleshooting?▼

Yes, knowledge capture of resolved issues and their solutions is a core feature of structured debugging. Documenting the root cause and solution builds a knowledge base that improves future debugging efficiency and prevents recurring problems.

When should I not use a quick patch for software troubleshooting?▼

You should avoid quick patches for software troubleshooting whenever a critical test fails or system stability is at risk. Without systematic investigation and root cause analysis, superficial fixes waste time and frequently cause additional technical issues.

Related Skills

Explore More Software Engineering Skills→
LuminairPrimeLuminairPrime
1

investigate

Investigate software bugs through root-cause analysis and hypothesis testing.

Community
Advanced
ryanbreenryanbreen
7

systematic-debugging

Document kernel debugging investigations through Problem, Root Cause, Solution, and Evidence phases.

Community
Advanced
ClipboardHealthClipboardHealth
66

flaky-test-debugger

Diagnose intermittent test failures and recommend fixes from logs and code.

Official
Advanced
Mekann2904Mekann2904

log-analyzer

Analyze log files to extract error patterns and detect anomalies.

Community
Intermediate