skills.rest
electroheadfx
electroheadfxCOMMUNITY
Explore all skills by this author →
GitHub

gsd-debug

Diagnose software bugs with a structured workflow and persistent investigation state.

4|Updated Apr 11, 2026
Search Tags:#debugging#root cause#troubleshooting#subagents#checkpoints#session continuity
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-debug-electroheadfx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-debug
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-debug-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve software issues methodically while preserving progress across context resets, so debugging work does not restart from scratch.

Core Features & Use Cases

  • Systematic debugging: Follows a scientific method approach to isolate symptoms, test hypotheses, and identify root causes.
  • Persistent workflow state: Supports checkpointing and continuation so investigations can resume cleanly after interruptions.
  • Interactive triage: Maps structured user questions into Codex-compatible input flows when more information is needed.
  • Agent-based investigation: Uses specialized debug subagents for deeper analysis and session management when appropriate.
  • Use case: A developer asks for help with a failing feature, and the Skill collects symptoms, investigates the issue, and produces a reproducible root-cause report or guided fix path.

Quick Start

Use the gsd-debug skill to investigate the failing build and identify the root cause with a clear debugging plan.

Frequently Asked Questions about gsd-debug

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

FAQPage Schema
How do I debug software bugs without losing my investigation progress after a context reset?▼

Debug software bugs using a structured workflow with persistent checkpoints to save investigation state. This ensures your root cause analysis resumes cleanly after interruptions, preventing debugging work from restarting from scratch across context resets.

What is the best way to perform root cause analysis on a failing software feature?▼

Root cause analysis on a failing feature uses a scientific method approach to isolate symptoms, test hypotheses, and identify root causes. It collects symptoms through structured user questioning and specialized debug subagents to produce a reproducible root-cause report.

How does checkpointed troubleshooting work when diagnosing complex software issues?▼

Checkpointed troubleshooting works by applying a structured debugging workflow that maps user questions into input flows and uses safe artifact gating. This persistent investigation state allows methodical diagnosis to continue seamlessly across sessions.

Can I continue an unresolved debugging session if interactive input is unavailable?▼

You can continue unresolved debugging sessions when interactive input is unavailable by using safe artifact gating and subagent coordination. The workflow manages session continuity by mapping structured questions into compatible input flows automatically.

When do I need subagent coordination during software troubleshooting?▼

Subagent coordination is needed during software troubleshooting when deeper analysis and specialized session management are required. Debug subagents handle complex root cause investigations, ensuring methodical symptom isolation and hypothesis testing.

Related Skills

Explore More Software Engineering Skills→
NTCodingNTCoding
334

observability-first-debugging

Instrument software with logs and traces to debug runtime behavior.

Community
Basic
CaptainCrouton89CaptainCrouton89
25

debugging

Detect and resolve elusive bugs through structured debugging workflows.

Community
Basic
Pear-CommercePear-Commerce

gsd-debug

Persist debugging progress and hypotheses across AI context resets.

Official
Advanced
MartinNevlahaMartinNevlaha
1

resume

Resume interrupted spec or bug workflows by loading their current state.

Community
Advanced