Debugging Toolkit Smart Debug

What it does

The Debugging Toolkit Smart Debug skill assists AI agents in debugging software issues by providing expert-level guidance and automated analysis. It leverages advanced techniques like error pattern recognition, stack trace analysis, and component dependency mapping to generate ranked hypotheses about the root cause of problems. The skill also recommends appropriate debugging strategies based on issue characteristics and suggests optimal instrumentation points for further investigation.

When to use it

• When working on tasks or workflows specifically related to debugging toolkit smart debug.
• When needing guidance, best practices, or checklists for debugging toolkit smart debug.
• For triage of issues requiring root cause analysis, especially those involving complex interactions between components and services.

Key capabilities

• Error Pattern Recognition: Identifies common error patterns in code and logs.
• Stack Trace Analysis: Analyzes stack traces to determine probable causes of errors.
• Component Dependency Analysis: Maps dependencies between software components to understand the impact of failures.
• Hypothesis Generation: Generates ranked hypotheses (3-5) for potential root causes, including probability scores and falsification criteria.
• Debugging Strategy Recommendation: Suggests appropriate debugging strategies like interactive debugging, observability-driven analysis, time-travel debugging, chaos engineering, or statistical methods.
• Intelligent Instrumentation Suggestions: Recommends optimal locations for breakpoints and log points.

Example prompts

• "Analyze this error message: [paste error message here]"
• "I'm seeing intermittent failures in production; what are some possible causes?"
• "What debugging strategy would you recommend for a race condition?"

Tips & gotchas

• The skill is specifically designed for tasks related to "debugging toolkit smart debug." It’s not suitable for unrelated development or domain-specific problems.
• For detailed implementation guidance, consult the resources/implementation-playbook.md file.
• To get the most accurate results, provide clear goals, constraints, and all relevant inputs (error messages, reproduction steps, affected components).