skills.rest
NovusAevum
NovusAevumCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of software bugs through a four-phase debugging framework.

1|Updated Nov 10, 2025
Search Tags:#software engineering#debugging#problem solving#troubleshooting#root cause analysis#bug fixing#technical issues
One-click install
npx skills add https://github.com/NovusAevum/dev-agents-orchestration --skill systematic-debugging-novusaevum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/NovusAevum/dev-agents-orchestration/tree/main/configs/claude-code/skills/systematic-debugging
Command: npx skills add https://github.com/NovusAevum/dev-agents-orchestration --skill systematic-debugging-novusaevum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time, new bugs, and recurring issues caused by guessing and applying quick fixes. It enforces a rigorous, four-phase process to always identify the root cause of any technical issue (bugs, test failures, unexpected behavior) before attempting a solution, ensuring lasting stability.

Core Features & Use Cases

  • Four-Phase Framework: Guides you through Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, ensuring a thorough and scientific approach to problem-solving.
  • Anti-Shortcut Mandate: Explicitly warns against common pitfalls like "quick fixes," "trying multiple changes at once," or "skipping tests," even under intense time pressure, to prevent superficial solutions.
  • Architectural Problem Detection: Provides a critical checkpoint to question the underlying architecture if multiple fixes fail, preventing endless symptom patching and prompting deeper structural discussions.
  • Use Case: When a critical production bug emerges under immense time pressure, this skill ensures you resist the urge for a quick patch, guiding you to the actual problem and a lasting solution, ultimately saving more time and preventing recurrence.

Quick Start

I'm encountering an unexpected error in the auth module. Guide me through systematic debugging to find 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 a bug instead of just fixing the symptom?▼

Root cause analysis identifies the underlying issue behind a bug by systematically investigating what actually failed, not just the visible error. This Skill guides you through a four-phase framework—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—ensuring you understand why the problem occurred before applying any fix, which prevents recurring issues and wasted troubleshooting.

What's the best way to debug test failures and production bugs under time pressure?▼

Systematic debugging enforces a structured process that resists quick fixes even when time is tight. It mandates completing root cause investigation before implementation, includes checkpoints to detect architectural problems, and explicitly warns against common shortcuts like trying multiple changes simultaneously or skipping validation, ultimately saving time by preventing new bugs.

How do I stop applying temporary patches that keep the same bug recurring?▼

Recurring bugs stem from treating symptoms rather than root causes. This framework includes pattern analysis to identify whether issues repeat across different modules or contexts, and an architectural checkpoint that prompts deeper structural review if multiple fixes fail, breaking the cycle of symptom patching.

When should I question the architecture instead of continuing to fix individual bugs?▼

When multiple targeted fixes fail to resolve an issue, architectural problems may be the underlying cause. This Skill provides an explicit critical checkpoint to evaluate whether the system design itself requires restructuring rather than incremental bug fixes, preventing endless troubleshooting of symptoms rooted in deeper design flaws.

Can I use this debugging approach for build failures and integration issues?▼

Yes. This four-phase framework applies to test failures, production bugs, unexpected behavior, performance problems, build failures, and integration issues. The structured root cause investigation process works across all technical failure modes, not just application-level bugs.

What anti-patterns does systematic debugging help me avoid?▼

The framework explicitly warns against guessing, applying quick fixes without investigation, trying multiple changes at once without isolating variables, and skipping validation steps. It enforces a rigorous scientific approach that documents anti-shortcut mandates to prevent superficial solutions that appear to work but leave root causes unresolved.

Related Skills

Explore More Software Engineering Skills→
BrunoAMSilvaBrunoAMSilva

systematic-debugging

Diagnose software bugs through root cause analysis and systematic error investigation.

Community
Intermediate
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
ShmurdocShmurdoc

gstack-openclaw-investigate

Enforces hypothesis-driven root cause investigation before code fixes in debugging workflows.

Community
Advanced