skills.rest
global-ministries
global-ministriesCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide four-phase debugging from investigation to implementation for software issues.

Updated Aug 17, 2025
Search Tags:#testing#debugging#investigation#root cause#troubleshooting#bug fixing
One-click install
npx skills add https://github.com/global-ministries/global-connect --skill systematic-debugging-global-ministries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/global-ministries/global-connect/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/global-ministries/global-connect --skill systematic-debugging-global-ministries

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by random fixes or quick patches that only address symptoms of underlying issues. It ensures you find and fix the root cause of any bug, test failure, or unexpected behavior.

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 before proposing any fixes.
  • Pressure Resistance: Includes anti-patterns and specific language to prevent shortcuts under time pressure.
  • Use Case: When a critical production bug appears, use this Skill to systematically investigate and ensure the correct root cause is identified and fixed, preventing recurrence and saving hours of debugging time.

Quick Start

Use the systematic debugging skill to investigate any bug 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 the symptom?▼

Root cause debugging requires a structured methodology that prioritizes investigation over quick patches. This Skill enforces a four-phase process—investigation, pattern analysis, hypothesis formation, and implementation—to ensure you fix the fundamental issue and prevent future recurrence.

What is the best way to systematically debug a critical production bug?▼

Systematic debugging of a production bug involves resisting time pressure to avoid random fixes. This Skill provides specific anti-patterns and language rules to guide you through a thorough investigation, ensuring the correct root cause is identified before any implementation changes are made.

Can I use this systematic debugging methodology for test failures and performance problems?▼

Yes, this systematic debugging methodology is applicable to all technical issues, including test failures, production bugs, and performance problems. It adapts its investigation and hypothesis phases to handle any unexpected software behavior by focusing on root cause analysis.

How do I stop myself or my team from taking shortcuts when troubleshooting issues under time pressure?▼

Troubleshooting under time pressure often leads to symptom-fixing and new bugs. This Skill includes built-in pressure resistance mechanisms, utilizing specific anti-patterns and language rules to prevent shortcuts and ensure a thorough four-phase debugging process is followed.

What steps should I follow to investigate a bug before proposing a fix?▼

Investigating a bug before proposing fixes requires following a structured four-phase process: investigation, pattern analysis, hypothesis formation, and implementation. This methodology ensures you thoroughly analyze the issue and form a validated hypothesis before writing any code.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

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

Official
Advanced
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
justinsenseijustinsensei
1

runtime-debugging

Step through Python and Node.js code with breakpoints and inspection.

Community
Intermediate