skills.rest
amanpal3
amanpal3COMMUNITY
Explore all skills by this author →
GitHub

debugger

Diagnose software bugs through systematic hypothesis testing and persistent state tracking.

1|Updated Sep 3, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#bug fixing#hypothesis testing#state tracking
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill debugger-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/gsd/.agents/skills/debugger
Command: npx skills add https://github.com/amanpal3/SKILLs --skill debugger-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into guesswork, tunnel vision, and repeated failed fixes. This Skill enforces a disciplined investigation process that finds root causes instead of masking symptoms, and preserves debugging state across sessions. ## Core Features & Use Cases - Hypothesis Testing: Form falsifiable hypotheses, gather evidence, and eliminate theories systematically using techniques like binary search, minimal reproduction, and differential debugging. - Persistent State Tracking: Maintain DEBUG.md and STATE.md files recording symptoms, eliminated hypotheses, and evidence so progress survives context resets. - 3-Strike Rule & Restart Protocol: After three failed fix attempts, stop, document findings, and restart with fresh context to escape polluted mental models. - Use Case: When a React counter increments twice per click, use this Skill to form specific hypotheses (e.g., double state update from remounting), test each one, and document the verified root cause. ## Quick Start Ask the agent to debug the reported issue using the systematic GSD debugging workflow and track findings in DEBUG.md.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I debug a bug systematically instead of guessing?▼

Form multiple falsifiable hypotheses before investigating, then test one variable at a time while documenting evidence. Techniques like minimal reproduction, binary search, and working backwards from expected output isolate the root cause methodically.

What should I do after multiple failed fix attempts?▼

Apply the 3-strike rule: stop the current approach, document what was tried in DEBUG.md, summarize findings to STATE.md, and restart with a fresh session. A fresh context often spots what a polluted context cannot.

How do I debug code that I wrote myself?▼

Treat your own code as foreign and read it as if someone else wrote it. Question your design decisions, prioritize recently modified lines as prime suspects, and accept that your mental model may not match actual behavior.

When should I restart a debugging session from scratch?▼

Restart after two hours without progress, three failed fixes, inability to explain current behavior, or when a fix works for unknown reasons. Document known facts and ruled-out hypotheses before beginning again.

How do I verify a bug fix is actually complete?▼

Confirm the bug reproduced before the fix, no longer reproduces after it, related functionality still works, and edge cases pass. A fix you cannot explain is luck, not a resolution.

Related Skills

Explore More Software Engineering Skills→
pcasarettopcasaretto

bug-reproduction-validator

Reproduce reported software issues and classify them as bugs, environmental problems, or user errors.

Community
Advanced
carlosamesarcarlosamesar
1

gd-debugger

Diagnoses software bugs and verifies minimal code changes with regression tests.

Community
Advanced
tykisgodtykisgod
10

test

Run Unity EditMode and PlayMode tests with filtering and Editor.log error scanning.

Community
Advanced
JhabbigJhabbig

debugging-strategies

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

Community
Advanced