skills.rest
da-moon
da-moonCOMMUNITY
Explore all skills by this author →
GitHub

gsd-debugger

Diagnose bugs with structured workflows for hypothesis testing and root-cause documentation.

1|Updated Mar 26, 2026
Search Tags:#debugging#root-cause#forensics#log-analysis#health-checks#bug-diagnosis
One-click install
npx skills add https://github.com/da-moon/manus-skills --skill gsd-debugger-da-moon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-debugger
Source: https://github.com/da-moon/manus-skills/tree/main/skills/gsd-debugger
Command: npx skills add https://github.com/da-moon/manus-skills --skill gsd-debugger-da-moon

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This debugging skill helps engineering teams identify, analyze, and resolve software issues quickly by providing structured workflows and forensic analysis templates.

Core Features & Use Cases

  • Diagnostic workflow: symptom collection, hypothesis testing, and root-cause documentation.
  • Forensic analysis: health checks, log analysis, and evidence-based resolution steps.
  • Use Case: When tests fail or behavior diverges, the skill guides a reproducible debugging sprint and post-mortem.

Quick Start

Tell me you found a bug and follow the debugging workflow to diagnose and resolve it.

Frequently Asked Questions about gsd-debugger

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

FAQPage Schema
How do I systematically debug a software issue and find the root cause?▼

Systematic debugging applies a structured workflow to diagnose software issues, utilizing symptom collection, health checks, and hypothesis-driven investigation to isolate and document the root cause.

What is the best way to analyze application logs for bug diagnosis?▼

Bug diagnosis through log analysis involves forensic examination of error patterns and health checks to identify evidence-based resolution steps and uncover the underlying project issue.

How do I document a post-mortem after resolving a complex codebase bug?▼

Documenting a post-mortem requires recording the reproducible debugging sprint, explicit hypothesis testing steps, and the final root-cause investigation to create comprehensive project documentation.

Can I use a structured debugging workflow for failing tests and unexpected behavior?▼

A structured debugging workflow is designed for exactly when tests fail or behavior diverges, guiding you through a reproducible debugging sprint to resolve the issue.

Does hypothesis-driven investigation work for any codebase or project ecosystem?▼

Hypothesis-driven investigation applies to codebases and project ecosystems of any scale, providing structured symptom collection and forensic analysis to resolve divergent behavior.

Related Skills

Explore More Software Engineering Skills→
tropekstropeks

investigate

Guide engineers through structured four-phase root-cause debugging from symptoms to verification.

Community
Advanced
meaganewallermeaganewaller
3

root-cause

Perform structured root cause analysis using 5-Whys methodology.

Community
Advanced
chiphwang1chiphwang1

oke-troubleshooter

Diagnose OKE incidents by correlating Kubernetes symptoms with OCI infrastructure signals.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate