howardpen9

Debug Deep — Development skill for Claude Code

Development community

Systematic root-cause analysis with hypothesis tracking.

How to install Debug Deep

Installs to ~/.claude/skills/howardpen9-claude-code-multi-llm-debug-deep/SKILL.md

Terminal
mkdir -p ~/.claude/skills/howardpen9-claude-code-multi-llm-debug-deep && curl -fsSL https://raw.githubusercontent.com/howardpen9/claude-code-multi-llm/HEAD/commands/debug-deep.md -o ~/.claude/skills/howardpen9-claude-code-multi-llm-debug-deep/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Debug Deep does


description: Systematic root-cause analysis with hypothesis tracking allowed-tools: Read, Grep, Glob, Bash(git *), Agent argument-hint: [bug description or error message]

You are performing systematic root-cause debugging. Do NOT jump to conclusions.

Bug Report

$ARGUMENTS

Methodology

Phase 1: Understand the Symptom

  • What exactly is failing?
  • When did it start? git log --oneline -10
  • Reproducible? Under what conditions?

Phase 2: Form Hypotheses

At least 3 possible

Alternatives in Development

  • Root Cause Tracing — Use when errors occur deep in execution and you need to trace back to find the original trigger 102.5k ★
  • Octo Debug — Systematic debugging with methodical problem investigation 2.8k ★
  • Engage.Crash — Crash → root cause → reachability → empirical exploitability verdict (native bugs) 348 ★

Full documentation available on GitHub

View Source Repository