gsd-debug

Coordinate persistent-state debugging across context resets with checkpoints.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-debug-trucol270
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-debug
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-debug-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug issues with persistent state across context resets, enabling investigators to reproduce and isolate failures without losing progress.

Core Features & Use Cases

  • Orchestrates symptom gathering, spawns gsd-debugger subagent, handles checkpoints, and spawns continuations to drive investigations.
  • Provides persistent state across sessions to keep context fresh while preserving investigation history.
  • Supports diagnose-only mode to plan root cause and potential fixes before applying changes.

Quick Start

Provide issue details and start a new debugging session using the gsd-debug workflow.

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 state issues across context resets?▼

To debug persistent state across context resets, use a structured workflow with an orchestrator, debugger subagent, and continuation agents to manage symptoms, checkpoints, and fixes without losing investigation progress.

What is checkpoint-driven debugging and when do I need it?▼

Checkpoint-driven debugging saves investigation progress at staged intervals, which is needed for reproducing and isolating failures across multiple sessions or context resets without losing investigation history.

How do I start a new debugging session for reproducible context?▼

To start a new debugging session for reproducible context, provide issue details and initiate the workflow to gather symptoms, spawn the debugger subagent, and handle checkpoints.

Can I diagnose root causes without applying fixes?▼

Yes, you can diagnose root causes without applying fixes by using a diagnose-only mode to plan the root cause and potential fixes before applying any changes.

Does stateful debugging work for investigations spanning multiple sessions?▼

Stateful debugging works for multi-session investigations by providing persistent state to keep context fresh while preserving investigation history across resets.

What are the limitations of debugging across context resets?▼

Debugging across context resets relies on checkpoint-driven progress and structured orchestration, meaning investigations must follow staged fixes and reproducible context workflows rather than ad-hoc methods.