skills.rest
LuuKhoaHoc
LuuKhoaHocCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

GSD Debugger

Guide systematic debugging through hypothesis testing and evidence gathering.

Updated Mar 11, 2026
Search Tags:#debugging#investigation#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/LuuKhoaHoc/erp-template --skill gsd-debugger-luukhoahoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: GSD Debugger
Source: https://github.com/LuuKhoaHoc/erp-template/tree/main/.agent/skills/debugger
Command: npx skills add https://github.com/LuuKhoaHoc/erp-template --skill gsd-debugger-luukhoahoc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, systematic approach to debugging complex software issues, moving beyond guesswork to root cause analysis.

Core Features & Use Cases

  • Hypothesis-driven investigation: Encourages forming falsifiable hypotheses and testing them rigorously.
  • Cognitive bias mitigation: Guides users to avoid common pitfalls like confirmation bias.
  • Systematic process: Outlines clear steps for investigation, reproduction, and verification.
  • Use Case: When a critical bug appears in production, this Skill helps engineers methodically uncover the root cause, document their findings, and ensure a robust fix.

Quick Start

Use the GSD Debugger skill to help me debug an issue where the user profile is not updating correctly after a save operation.

Frequently Asked Questions about GSD Debugger

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

FAQPage Schema
What is systematic debugging and how does it help with root cause analysis?▼

Hypothesis-driven investigation guides you to form falsifiable hypotheses and test them rigorously. By systematically gathering evidence and mitigating cognitive biases like confirmation bias, it ensures thorough bug verification.

How do I debug a complex software issue using a systematic process?▼

Systematic debugging replaces guesswork with structured root cause analysis by employing hypothesis testing and evidence gathering. This approach ensures thorough verification and helps uncover the true origin of complex software issues.

What is the best way to document a bug investigation to avoid cognitive bias?▼

The best way to document a bug investigation is using structured formats like DEBUG.md. This tracks persistent state, mitigates cognitive biases such as confirmation bias, and records hypotheses alongside evidence.

Does this systematic debugging approach work for critical production bugs?▼

Yes, this systematic debugging approach works for critical production bugs. It helps engineers methodically uncover the root cause, document findings in DEBUG.md, and ensure a robust fix through disciplined investigation.

Why should I use hypothesis testing for software troubleshooting instead of guessing?▼

You should use hypothesis testing for software troubleshooting because it moves beyond guesswork to root cause analysis. It guides you through rigorous evidence gathering and persistent state tracking to avoid cognitive biases.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
RDCrystalLabRDCrystalLab

debug-hypothesis

Structure debugging investigations with evidence-driven root cause analysis.

Official
Advanced
jayhjenkinsjayhjenkins

Jay-Dev QA Testing Skill

Automate three-tier QA testing with TEST_INDEX.md and RUNS/ reports.

Community
Intermediate
akiyoshiakiyoshi

canary

Monitor a production URL for anomalies during the first 10 minutes post-deploy.

Community
Advanced