debug-like-expert — Claude Code skill: methodical debugging
debug-like-expert activates a structured debugging protocol for complex issues when standard troubleshooting fails. Gathers evidence, tests hypotheses, and finds root causes instead of applying quick fixes.
MIT ★ 1,988 updated 2026-04-01
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resourcesWhat debug-like-expert does
debug-like-expert shifts your mindset to that of a senior engineer: instead of guessing at causes, you verify each hypothesis systematically. The skill starts by mapping current state—exact error messages, reproduction steps, expected vs. actual output. It traces execution paths through all components, reads relevant code completely, and gathers context about dependencies and configuration.
A critical feature: if you wrote the code being debugged, the skill demands more skepticism toward your implementation than toward unfamiliar code. Your mental model of how it "should work" can mask what it actually does. The skill cuts through this cognitive bias by framing hypotheses based on evidence, not intent.
The skill includes a context scanner that detects your project type (Python, Rust, JavaScript, Swift, Go, Java) and loads domain-specific knowledge—common errors, debugging techniques, and pitfalls for that language or framework. If the domain isn't obvious, it offers a menu or proceeds with general methodology.
What it helps with
- find root cause instead of applying surface-level fixes
- defer fixes until you understand the problem completely
- test each hypothesis systematically through logs and output
- overcome cognitive biases when debugging your own code
- load domain expertise for common errors in your language
Example prompts for the agent
- I've spent hours on this error and standard debugging isn't working—let me activate debug-like-expert
- Fixes work, but I don't understand why the problem happened—help me trace it methodically
- We have a Rust project with weird memory behavior—run the skill with domain knowledge for systems programming
How to install debug-like-expert
1Plugin marketplace
/plugin marketplace add glittercowboy/taches-cc-resources/plugin install taches-cc-resources@taches-cc-resourcesThis installs the whole taches-cc-resources plugin with all its skills
2Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill debug-like-expert -a claude-code3Manually: put the files in place
~/.claude/skills/debug-like-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debug-like-expert/
1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill debug-like-expert -a codex2Manually: put the files in place
.agents/skills/debug-like-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill debug-like-expert -a cursor2Manually: put the files in place
.cursor/skills/debug-like-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install glittercowboy/taches-cc-resources skills/debug-like-expert2Manually: put the files in place
.github/skills/debug-like-expert/SKILL.md1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill debug-like-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/glittercowboy/taches-cc-resources --path skills/debug-like-expertManually: put the files in place
.devin/skills/debug-like-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debug-like-expert
How do I install debug-like-expert in Claude Code?
Run in order: /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources. Alternatively: npx skills add glittercowboy/taches-cc-resources --skill debug-like-expert -a claude-code or open ~/.claude/skills/debug-like-expert/SKILL.md.
Why use debug-like-expert if I debug code myself?
The skill enforces scientific method over intuition: it documents exact behavior, traces execution fully, and tests each hypothesis. Crucially, it requires skepticism toward your own code—something easily skipped when you're debugging your own work.
Does debug-like-expert support my programming language?
The skill covers Python, JavaScript, TypeScript, Rust, Swift, Go, C/C++, and Java. On launch, it scans your project, identifies the language, and loads domain expertise—known pitfalls, debugging tools, and performance patterns for that stack.
Source text
SKILL.md · MIT
---
name: debug-like-expert
description: Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
---
<objective>
Deep analysis debugging mode for complex issues. This skill activates methodical investigation protocols with evidence gathering, hypothesis testing, and rigorous verification when standard troubleshooting has failed.
The skill emphasizes treating code you wrote with MORE skepticism than unfamiliar code, as cognitive biases about "how it should work" can blind you to actual implementation errors. Use scientific method to systematically identify root causes rather than applying quick fixes.
</objective>
<context_scan>
**Run on every invocation to detect domain-specific debugging expertise:**
```bash
# What files are we debugging?
echo "FILE_TYPES:"
find . -maxdepth 2 -type f 2>/dev/null | grep -E '\.(py|js|jsx|ts|tsx|rs|swift|c|cpp|go|java)$' | head -10
# Check for domain indicators
[ -f "package.json" ] && echo "DETECTED: JavaScript/Node project"
[ -f "Cargo.toml" ] && echo "DETECTED: Rust project"
[ -f "setup.py" ] || [ -f "pyproject.toml" ] && echo "DETECTED: Python project"
[ -f "*.xcodeproj" ] || [ -f "Package.swift" ] && echo "DETECTED: Swift/macOS project"
[ -f "go.mod" ] && echo "DETECTED: Go project"
# Scan for available domain expertise
echo "EXPERTISE_SKILLS:"
ls ~/.claude/skills/expertise/ 2>/dev/null | head -5
```
**Present findings before starting investigation.**
</context_scan>
<domain_expertise>
**Domain-specific expertise lives in `~/.claude/skills/expertise/`**
Domain skills contain comprehensive knowledge including debugging, testing, performance, and common pitfalls. Before investigation, determine if domain expertise should be loaded.
<scan_domains>
```bash
ls ~/.claude/skills/expertise/ 2>/dev/null
```
This reveals available domain expertise (e.g., macos-apps, iphone-apps, python-games, unity-games).
**If no expertise skills found:** Proceed without domain expertise (graceful degradation). The skill works fine with general debugging methodology.
</scan_domains>
<inference_rules>
If user's description or codebase contains domain keywords, INFER the domain:
| Keywords/Files | Domain Skill |
|----------------|--------------|
| "Python", "game", "pygame", ".py" + game loop | expertise/python-games |
| "React", "Next.js", ".jsx/.tsx" | expertise/nextjs-ecommerce |
| "Rust", "cargo", ".rs" files | expertise/rust-systems |
| "Swift", "macOS", ".swift" + AppKit/SwiftUI | expertise/macos-apps |
| "iOS", "iPhone", ".swift" + UIKit | expertise/iphone-apps |
| "Unity", ".cs" + Unity imports | expertise/unity-games |
| "SuperCollider", ".sc", ".scd" | expertise/supercollider |
| "Agent SDK", "claude-agent" | expertise/with-agent-sdk |
If domain inferred, confirm:
```
Detected: [domain] issue → expertise/[skill-name]
Load this debugging expertise? (Y / see other options / none)
```
</inference_rules>
<no_inference>
If no domain obvious, present options:
```
What type of project are you debugging?
Available domain expertise:
1. macos-apps - macOS Swift (SwiftUI, AppKit, debugging, testing)
2. iphone-apps - iOS Swift (UIKit, debugging, performance)
3. python-games - Python games (Pygame, physics, performance)
4. unity-games - Unity (C#, debugging, optimization)
[... any others found in build/]
N. None - proceed with general debugging methodology
C. Create domain expertise for this domain
Select:
```
</no_inference>
<load_domain>
When domain selected, READ all references from that skill:
```bash
cat ~/.claude/skills/expertise/[domain]/references/*.md 2>/dev/null
```
This loads comprehensive domain knowledge BEFORE investigation:
- Common issues and error patterns
- Domain-specific debugging tools and techniques
- Testing and verification approaches
- Performance profiling and optimization
- Known pitfalls and anti-patterns
- Platform-specific considerations
Announce: "Loaded [domain] expertise. Investigating with domain-specific context."
**If domain skill not found:** Inform user and offer to proceed with general methodology or create the expertise.
</load_domain>
<when_to_load>
Domain expertise should be loaded BEFORE investigation when domain is known.
Domain expertise is NOT needed for:
- Pure logic bugs (domain-agnostic)
- Generic algorithm issues
- When user explicitly says "skip domain context"
</when_to_load>
</domain_expertise>
<context>
This skill activates when standard troubleshooting has failed. The issue requires methodical investigation, not quick fixes. You are entering the mindset of a senior engineer who debugs with scientific rigor.
**Important**: If you wrote or modified any of the code being debugged, you have cognitive biases about how it works. Your mental model of "how it should work" may be wrong. Treat code you wrote with MORE skepticism than unfamiliar code - you're blind to your own assumptions.
</context>
<core_principle>
**VERIFY, DON'T ASSUME.** Every hypothesis must be tested. Every "fix" must be validated. No solutions without evidence.
**ESPECIALLY**: Code you designed or implemented is guilty until proven innocent. Your intent doesn't matter - only the code's actual behavior matters. Question your own design decisions as rigorously as you'd question anyone else's.
</core_principle>
<quick_start>
<evidence_gathering>
Before proposing any solution:
**A. Document Current State**
- What is the EXACT error message or unexpected behavior?
- What are the EXACT steps to reproduce?
- What is the ACTUAL output vs EXPECTED output?
- When did this start working incorrectly (if known)?
**B. Map the System**
- Trace the execution path from entry point to failure point
- Identify all components involved
- Read relevant source files completely, not just scanning
- Note dependencies, imports, configurations affecting this area
**C. Gather External Knowledge (when needed)**
- Use MCP servers for API documentation, library details, or domain knowledge
- Use web search for error messages, framework-specific behaviors, or recent changes
- Check official docs for intended behavior vs what you observe
- Look for known issues, breaking changes, or version-specific quirks
See [references/when-to-research.md](references/when-to-research.md) for detailed guidance on research strategy.
</evidence_gathering>
<root_cause_analysis>
**A. Form Hypotheses**
Based on evidence, list possible causes:
1. [Hypothesis 1] - because [specific evidence]
2. [Hypothesis 2] - because [specific evidence]
3. [Hypothesis 3] - because [specific evidence]
**B. Test Each Hypothesis**
For each hypothesis:
- What would prove this true?
- What would prove this false?
- Design a minimal test
- Execute and document results
See [references/hypothesis-testing.md](references/hypothesis-testing.md) for scientific method application.
**C. Eliminate or Confirm**
Don't move forward until you can answer:
- Which hypothesis is supported by evidence?
- What evidence contradicts other hypotheses?
- What additional information is needed?
</root_cause_analysis>
<solution_development>
**Only after confirming root cause:**
**A. Design Solution**
- What is the MINIMAL change that addresses the root cause?
- What are potential side effects?
- What could this break?
**B. Implement with Verification**
- Make the change
- Add logging/debugging output if needed to verify behavior
- Document why this change addresses the root cause
**C. Test Thoroughly**
- Does the original issue still occur?
- Do the reproduction steps now work?
- Run relevant tests if they exist
- Check for regressions in related functionality
See [references/verification-patterns.md](references/verification-patterns.md) for comprehensive verification approaches.
</solution_development>
</quick_start>
<critical_rules>
1. **NO DRIVE-BY FIXES**: If you can't explain WHY a change works, don't make it
2. **VERIFY EVERYTHING**: Test your assumptions. Read the actual code. Check the actual behavior
3. **USE ALL TOOLS**:
- MCP servers for external knowledge
- Web search for error messages, docs, known issues
- Extended thinking ("think deeply") for complex reasoning
- File reading for complete context
4. **THINK OUT LOUD**: Document your reasoning at each step
5. **ONE VARIABLE**: Change one thing at a time, verify, then proceed
6. **COMPLETE READS**: Don't skim code. Read entire relevant files
7. **CHASE DEPENDENCIES**: If the issue involves libraries, configs, or external systems, investigate those too
8. **QUESTION PREVIOUS WORK**: Maybe the earlier "fix" was wrong. Re-examine with fresh eyes
</critical_rules>
<success_criteria>
Before starting:
- [ ] Context scan executed to detect domain
- [ ] Domain expertise loaded if available and relevant
During investigation:
- [ ] Do you understand WHY the issue occurred?
- [ ] Have you verified the fix actually works?
- [ ] Have you tested the original reproduction steps?
- [ ] Have you checked for side effects?
- [ ] Can you explain the solution to someone else?
- [ ] Would this fix survive code review?
If you can't answer "yes" to all of these, keep investigating.
**CRITICAL**: Do NOT mark debugging tasks as complete until this checklist passes.
</success_criteria>
<output_format>
```markdown
## Issue: [Problem Description]
### Evidence
[What you observed - exact errors, behaviors, outputs]
### Investigation
[What you checked, what you found, what you ruled out]
### Root Cause
[The actual underlying problem with evidence]
### Solution
[What you changed and WHY it addresses the root cause]
### Verification
[How you confirmed this works and doesn't break anything else]
```
</output_format>
<advanced_topics>
For deeper topics, see reference files:
**Debugging mindset**: [references/debugging-mindset.md](references/debugging-mindset.md)
- First principles thinking applied to debugging
- Cognitive biases that lead to bad fixes
- The discipline of systematic investigation
- When to stop and restart with fresh assumptions
**Investigation techniques**: [references/investigation-techniques.md](references/investigation-techniques.md)
- Binary search / divide and conquer
- Rubber duck debugging
- Minimal reproduction
- Working backwards from desired state
- Adding observability before changing code
**Hypothesis testing**: [references/hypothesis-testing.md](references/hypothesis-testing.md)
- Forming falsifiable hypotheses
- Designing experiments that prove/disprove
- What makes evidence strong vs weak
- Recovering from wrong hypotheses gracefully
**Verification patterns**: [references/verification-patterns.md](references/verification-patterns.md)
- Definition of "verified" (not just "it ran")
- Testing reproduction steps
- Regression testing adjacent functionality
- When to write tests before fixing
**Research strategy**: [references/when-to-research.md](references/when-to-research.md)
- Signals that you need external knowledge
- What to search for vs what to reason about
- Balancing research time vs experimentation
</advanced_topics>
© Lex Christopherson · MIT · glittercowboy/taches-cc-resources