skills.rest
OctavianTocan
OctavianTocanCOMMUNITY
Explore all skills by this author →
Website𝕏@theoctaviantocGitHub

systematic-debugging

Guide a four-phase debugging process to identify and fix root causes.

3|Updated Dec 24, 2025
Search Tags:#debugging#investigation#root cause#troubleshooting#bug fixing#systematic process
One-click install
npx skills add https://github.com/OctavianTocan/ai-nexus --skill systematic-debugging-octaviantocan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/OctavianTocan/ai-nexus/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/OctavianTocan/ai-nexus --skill systematic-debugging-octaviantocan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring that the root cause of any issue is identified and fixed, rather than just addressing the immediate symptom. It provides a structured, pressure-resistant process for debugging.

Core Features & Use Cases

  • Systematic Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue, not just a quick patch.
  • Pressure Resistance: Includes rules and language designed to prevent shortcuts under time pressure.
  • Use Case: When a critical bug appears in production, this Skill ensures a thorough investigation to prevent recurring issues, rather than a hasty, incomplete fix.

Quick Start

Use the systematic debugging skill to investigate any bug or unexpected behavior before proposing fixes.

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 bug instead of just fixing symptoms?▼

Systematic debugging prevents wasted time by guiding you through investigation, pattern analysis, hypothesis formation, and implementation, ensuring you fix the fundamental issue rather than just the immediate symptom.

What is the best way to debug complex multi-component systems?▼

The best way to debug multi-component systems is to trace data flow across components and question the architecture if multiple fixes fail, ensuring you identify the fundamental issue rather than applying patches.

How do I prevent introducing new bugs when troubleshooting production issues?▼

Prevent new bugs during troubleshooting by following a pressure-resistant process that mandates root cause identification before implementation, avoiding hasty and incomplete fixes that cause recurring issues.

Can I use a systematic debugging process for intermittent technical issues?▼

Yes, a systematic debugging process handles intermittent technical issues by using pattern analysis during the investigation phase to identify recurring behaviors and formulate accurate root cause hypotheses.

When should I question architecture during bug fixing?▼

You should question architecture during bug fixing when multiple fixes fail to resolve the issue, indicating the fundamental design rather than a specific component is causing the root problem.

Related Skills

Explore More Software Engineering Skills→
thongpham95thongpham95

vibe-debugger

Automate bug investigation workflows with human review phases and generate BUG_REPORT.md files.

Community
Basic
tollusettolluset

bug-fix

Reproduce software defects, perform root cause analysis, and implement verified fixes.

Community
Intermediate
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
xlelibertyxleliberty

systematic-debugging

Identify and resolve technical issues through a four-phase debugging framework.

Community
Advanced