One-click install
npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-debug-abdelrhmanuzaki
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/AbdelrhmanUZaki/KnowledgeNuggets/tree/main/2-setup/shared/codex/skills/gsd-debug
Command: npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-debug-abdelrhmanuzaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging sessions often lose progress when AI context windows reset, forcing you to re-explain symptoms and re-run investigations. This Skill orchestrates systematic debugging with persistent checkpoint state, so investigations survive context resets and can be resumed at any time. ## Core Features & Use Cases - Scientific Method Debugging: Spawns an isolated gsd-debugger subagent that investigates bugs systematically rather than guessing at fixes. - Persistent Session Management: Supports list, status <slug>, and continue <slug> subcommands to track and resume debug sessions stored under .planning/debug/. - Diagnose-Only Mode: The --diagnose flag returns a Root Cause Report without applying any fix, useful when you want analysis before changes. - Use Case: You hit a failing test in a large codebase. Invoke the skill with the symptom description, let the debugger agent isolate the root cause, then continue the session the next day without losing any investigation state. ## Quick Start Invoke $gsd-debug followed by a description of the bug symptoms to start a systematic debugging session.

Frequently Asked Questions about gsd-debug

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

FAQPage Schema
How do I debug an issue systematically with an AI agent?ā–¼

Invoke $gsd-debug followed by a description of the symptoms. The skill spawns a gsd-debugger subagent that applies the scientific method in an isolated context, then reports checkpoints back to the orchestrator.

How do I resume a previous debugging session after a context reset?ā–¼

Use the subcommands `list` to see active sessions, `status <slug>` to inspect one, and `continue <slug>` to resume it. Session state is persisted as markdown files under .planning/debug/.

Can I get a root cause analysis without applying a fix?ā–¼

Yes, pass the --diagnose flag with your bug description. The skill returns a Root Cause Report only and does not modify any code.

What happens if the interactive question tool is unavailable during debugging?ā–¼

The skill stops and presents questions as a plain-text numbered list, then waits for your reply. It will not write workflow artifacts or silently pick defaults unless you passed --auto or --all.

Does this skill spawn subagents automatically?ā–¼

Subagent spawning via spawn_agent only occurs when the user has explicitly requested sub-agents. Otherwise the investigation is performed inline in the current agent rather than forcing a spawn.