Debugging

What it does

This skill automates debugging of Lobbi Docs test suite failures by analyzing logs and suggesting potential root causes. It provides comprehensive debugging capabilities, including an option for “extended thinking” which leverages Claude's deeper reasoning mode to handle complex scenarios requiring more in-depth analysis. The skill uses a structured hypothesis-driven framework to systematically investigate issues.

When to use it

• Error troubleshooting when the root cause is unclear or involves multiple possibilities.
• Analyzing logs to identify patterns and potential problems.
• Debugging performance slowdowns where bottlenecks are not immediately obvious.
• Investigating bugs in distributed systems that span multiple services.
• Addressing complex, multi-layered bugs involving intricate state transitions or side effects.

Key capabilities

• Log analysis for error identification.
• Hypothesis generation for potential root causes.
• Structured debugging framework (Observation, Hypothesis Generation, Systematic Testing, Root Cause Identification, Fix + Validation).
• "Extended thinking" mode using Claude to provide systematic hypothesis generation and cross-domain insights (network, application, infrastructure).
• MECE (Mutually Exclusive, Collectively Exhaustive) bug analysis templates.

Example prompts

• “Claude, please use extended thinking to help debug this issue: [Describe the problem with symptoms, context, and what you've tried].”
• "Analyze these logs and generate 3-5 plausible hypotheses for why our tests are failing."
• "Using the MECE bug analysis template, can you analyze this error message?"

Tips & gotchas

• For complex issues with unclear failure patterns or intermittent problems, enable "extended thinking" in your prompt.
• The skill relies on providing sufficient context and details about the problem to generate accurate hypotheses.
• Follow the structured debugging framework for more effective troubleshooting of intricate bugs.