skills.rest
tDalile
tDalileCOMMUNITY
Explore all skills by this author →
GitHub

gsd:debug

Debug runtime failures and verification mismatches using the gsd-debugger agent.

Updated Aug 27, 2026
Search Tags:#troubleshooting#logs#verification#debug#root-cause#gsd-debugger
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-debug-tdalile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd:debug
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/commands/debug
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-debug-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identifies and resolves bugs and unexpected behavior by running a structured investigation using the gsd-debugger agent and diagnostic techniques to find root causes and verify fixes.

Core Features & Use Cases

  • Structured Investigation: Walks through describing the problem, executing the gsd-debugger agent, tracing execution flow, checking logs, and producing a minimal reproduction.
  • Verification & Validation: Applies fixes and verifies they resolve the issue to prevent regressions.
  • Use Case: Use when a script, agent, or CI workflow produces errors or fails verification; gather logs, reproduce the failure, identify the root cause, and confirm the repair.

Quick Start

Run the gsd:debug skill to describe the failure, execute the gsd-debugger agent, follow investigation steps, apply a fix, and verify the outcome.

Frequently Asked Questions about gsd:debug

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

FAQPage Schema
How do I systematically debug runtime failures and verification mismatches in agent workflows?▼

To debug runtime failures and verification mismatches, use structured investigation to describe the problem, run the gsd-debugger agent, examine traces and logs, reproduce minimal examples, and apply validated fixes.

What is the best way to perform root-cause analysis on unexpected script behaviors during CI runs?▼

Root-cause analysis for unexpected script behaviors during CI runs involves tracing execution flow, checking logs, producing a minimal reproduction of the failure, and verifying the applied fix prevents regressions.

How do I fix script errors and verify the repair to prevent future regressions?▼

Fix script errors by applying a targeted repair after identifying the root cause, then verify the outcome to confirm the issue is resolved and prevent regressions during development and CI runs.

Can I use this debugging approach for both development scripts and CI workflow failures?▼

Yes, this debugging approach applies to runtime failures, verification mismatches, and unexpected behaviors in scripts, agents, or workflows encountered during both development and CI runs.

What steps are needed to investigate and resolve unexpected agent behavior?▼

Investigating unexpected agent behavior requires describing the failure, executing the gsd-debugger agent, tracing execution flow, checking logs, and validating the applied fix against a minimal reproduction.

Related Skills

Explore More Software Engineering Skills→
cericocerico

debug

Trace execution paths to diagnose errors across code, APIs, and UI.

Community
Basic
LEEI1337LEEI1337
6

systematic-debugging

Identify root causes in technical issues before applying fixes.

Community
Basic
nahisahonahisaho
69

bug-hunter

Diagnose software bugs through investigation, reproduction, and root-cause analysis.

Community
Intermediate
loongclaw-ailoongclaw-ai
641

systematic-debugging

Investigate bugs and test failures systematically before applying fixes.

Official
Advanced