skills.rest
coolguy1771
coolguy1771COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide four-phase debugging from root cause investigation to fix implementation.

Updated Sep 24, 2021
Search Tags:#debugging#investigation#root cause#problem solving#troubleshooting#bug fixing
One-click install
npx skills add https://github.com/coolguy1771/dotfiles --skill systematic-debugging-coolguy1771
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/coolguy1771/dotfiles/tree/main/chezmoi/private_dot_cursor/skills/systematic-debugging
Command: npx skills add https://github.com/coolguy1771/dotfiles --skill systematic-debugging-coolguy1771

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a robust framework to systematically investigate and resolve any technical issue, preventing the common pitfalls of quick fixes and symptom treatment.

Core Features & Use Cases

  • Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental cause of a bug, not just patching the immediate problem.
  • Pressure Resistance: Includes specific language and structural defenses to prevent rationalization under time pressure or urgency.
  • Use Case: When a critical API endpoint starts returning errors, this Skill ensures the team doesn't just add a retry mechanism but thoroughly investigates why the endpoint is failing in the first place, preventing future occurrences.

Quick Start

Use the systematic-debugging skill to investigate any bug you encounter before proposing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and how does it help find the root cause of a bug?▼

Systematic debugging is a structured investigation methodology that traces data flow and gathers evidence to identify root causes rather than patching symptoms. It prevents quick fixes that mask underlying architectural problems.

How do I debug a critical API endpoint failure without just adding a retry mechanism?▼

Debug an API endpoint failure by following a four-phase methodology: investigation, pattern analysis, hypothesis formation, and implementation. This ensures you trace data flow and question architecture to find why the endpoint fails.

What's the best way to troubleshoot technical issues under time pressure without rationalizing?▼

The best way to troubleshoot under pressure is using a methodology with built-in structural defenses against rationalization. It enforces evidence gathering and hypothesis testing before allowing fixes, resisting urgency-driven shortcuts.

How do I investigate a bug when multiple fixes have already failed?▼

When multiple fixes fail, shift to architectural questioning during pattern analysis. Re-examine data flow tracing and fundamental assumptions to uncover systemic root causes that previous patches missed.

Can I use this structured debugging methodology for any technical problem?▼

Yes, this methodology applies to any technical issue requiring root cause investigation. It provides a general framework for problem solving across software engineering contexts without platform-specific constraints.

When should I avoid quick fixes during bug fixing?▼

Avoid quick fixes whenever a bug recurs or affects critical functionality. Use systematic investigation instead to form hypotheses from evidence, preventing symptom treatment that leads to future occurrences.

Related Skills

Explore More Software Engineering Skills→
LuminairPrimeLuminairPrime
1

investigate

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

Community
Advanced
haJ1thaJ1t

systematic-debugging

Diagnose bugs to verified root cause using reproduce-minimize-hypothesize-bisect-confirm.

Community
Advanced
Ouro-labsOuro-labs
14

ce-debug

Investigate codebase bugs through hypothesis testing and issue tracker integration.

Official
Advanced
hubeiqiaohubeiqiao

systematic-debugging

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

Community
Advanced