debug

Diagnoses root causes of bugs across multi-language projects and frameworks.

24|6|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/johnlindquist/claude --skill debug-johnlindquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/johnlindquist/claude/tree/main/skills/debug
Command: npx skills add https://github.com/johnlindquist/claude --skill debug-johnlindquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A comprehensive root cause debugging workflow that guides you through investigation, understanding, reasoning, and fixing.

Core Features & Use Cases

  • Structured investigative steps (rg, gh, gemini)
  • Systematic root-cause analysis
  • Generated fix recommendations

Quick Start

Follow the full-debug flow: Phase 1 codebase search, Phase 2 GitHub issues, Phase 3 reasoning, Phase 4 fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose the root cause of a bug in my codebase?

Root-cause debugging systematically investigates bugs through codebase search, issue tracking, and structured reasoning to identify the underlying problem rather than surface symptoms. This Skill enforces a four-phase protocol: investigate code patterns, understand context, reason about causes, and generate fixes with verification steps.

What's the best way to analyze logs and trace unexpected behavior across multiple files?

Structured log analysis traces unexpected behavior by searching relevant code sections, correlating evidence from version history, and applying disciplined reasoning to narrow causes. This approach produces confidence-rated root causes with recommended fixes and prevention guidance.

Can I use this debugging workflow across different programming languages and frameworks?

Yes, the root-cause debugging protocol applies across multi-language projects and various frameworks. It uses language-agnostic investigation techniques—codebase search, issue triage, and evidence-based reasoning—to diagnose bugs regardless of tech stack.

How do I move from identifying a bug to generating a fix?

After investigation and root-cause analysis, the workflow generates fix recommendations with specific verification steps and prevention guidance. This ensures fixes address the underlying cause and include testing strategies to prevent regression.

What does a structured debugging workflow prevent?

Disciplined root-cause analysis prevents treating symptoms as causes, avoids premature fixes, and reduces recurring bugs through prevention guidance. It enforces evidence-based reasoning so fixes target actual problems, not guesses.