Persist debugging progress and hypotheses across AI context resets.
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-debug-pear-commerce
Please help me install this Agent Skill. Skill: gsd-debug Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-debug Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-debug-pear-commerce
This Skill solves the common pain point of losing all debugging progress, hypotheses, and investigation state when an AI assistant's context resets mid-debugging session, eliminating the need to restart time-consuming investigations from scratch.
Invoke the gsd-debug skill by mentioning the gsd-debug command followed by a description of the issue you are debugging to start a new persistent investigation session or resume an existing active session if one is available.
High-intent search queries and answers about installing and using this skill.
To save debugging progress across context resets, you need a persistent state mechanism that stores hypotheses and checkpoints externally. This skill writes investigation state to a local .planning/debug/ directory, preserving session data for seamless resumption later.
Yes, you can isolate long-running software debugging sessions by spawning dedicated subagents. These subagents investigate issues independently, keeping the main conversation context free for direct user interaction while diagnostics run.
Subagent orchestration for multi-session debugging is the process of spawning isolated debugger agents to test hypotheses. It enables thorough investigations across context resets by saving state and using human verification checkpoints for accuracy.
You can resume a complex production bug investigation by loading previously saved session state. The skill automatically detects existing debug data in the .planning/debug/ directory and continues the investigation exactly where it left off.
Yes, this debugging workflow supports human verification checkpoints during root cause analysis. It pauses subagent investigation at critical stages, allowing you to verify findings before the session continues across context resets.
The best way to trace root cause across multiple debugging sessions is using a persistent debug state directory. This approach saves hypotheses and checkpoints externally, eliminating the need to re-explain issues or re-run initial diagnostics.
cloudofgeorgeIdentify root causes of bugs through structured investigation and evidence gathering.
shaythegay13Identify software issue root causes through symptom collection and code review.
SensLiaoVerify security mitigations for completed GSD-namespace workflow phases.
hthor213Capture mid-session AI development state and detect spec drift.
