gsd-debug

Debug software issues across context resets with structured session tracking.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-debug-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-debug
Command: npx skills add https://github.com/coco-research/coco --skill gsd-debug-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix software issues that are hard to resolve in a single pass, especially when context resets, partial evidence, or long-running investigations make it difficult to keep track of what has already been tried.

Core Features & Use Cases

  • Symptom Gathering: Collects expected behavior, actual behavior, errors, timeline, and reproduction steps before investigating.
  • Isolated Agent Debugging: Spawns a dedicated debugging agent so the main conversation stays focused while deeper investigation happens separately.
  • Checkpoint Handling: Supports human verification and continuation prompts when the investigation reaches a decision point.
  • Use Case: A developer reports a failing workflow after a recent change; this Skill can trace the issue, confirm root cause, and continue the fix across context resets without losing progress.

Quick Start

Use the gsd-debug skill to investigate the reported issue, gather the necessary symptoms, and either diagnose the root cause or apply a fix.

Frequently Asked Questions about gsd-debug

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

FAQPage Schema
How do I debug persistent software failures across context resets without losing progress?

To debug persistent failures across context resets, you need structured session tracking that preserves investigation state. This Skill uses checkpoint handling to save progress at decision points, allowing the debugging process to continue seamlessly even after context loss occurs.

What is the best way to isolate root cause analysis during a long-running troubleshooting session?

The best way to isolate root cause analysis is by spawning a dedicated subagent for deeper investigation. This isolated agent debugging approach keeps the main conversation focused while gathering symptoms and performing complex troubleshooting separately to reach a confirmed root cause.

How do I gather symptoms effectively before starting to investigate a reported software bug?

To gather symptoms effectively before investigating a bug, collect expected behavior, actual behavior, errors, timeline, and reproduction steps. This structured symptom gathering ensures the debugging agent has all necessary evidence to trace the issue and confirm the root cause before applying a fix.

Can I resume a debugging investigation after a context loss or session interruption?

Yes, you can resume a debugging investigation after a context loss using checkpoint handling. The Skill supports human verification and continuation prompts at decision points, allowing the isolated debugging agent to pick up the root cause analysis exactly where it left off.

Does structured debugging work for tracing issues in complex state management workflows?

Yes, structured debugging works for state management issues by using controlled Read, Bash, and Task tools to trace failures. It applies isolated subagent analysis to investigate recent changes and confirm the root cause of failing workflows before applying any fixes.