troubleshooting

Diagnose AIDB issues across adapters, test environments, CI/CD workflows, MCP servers, and the CLI.

19|2|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/ai-debugger-inc/aidb --skill troubleshooting-ai-debugger-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/ai-debugger-inc/aidb/tree/main/.claude/skills/troubleshooting
Command: npx skills add https://github.com/ai-debugger-inc/aidb --skill troubleshooting-ai-debugger-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When AIDB encounters unexpected behavior, identifying the root cause can be time-consuming and frustrating without a structured approach. This Skill provides a comprehensive troubleshooting guide, offering investigation workflows, log locations, common failure modes, and diagnostic commands to quickly pinpoint and resolve issues across all AIDB components. It helps users efficiently debug and minimize downtime.

Core Features & Use Cases

  • Structured Investigation Workflow: Follow a step-by-step playbook from reproduction to validation.
  • Comprehensive Log Reference: Know exactly where to find logs for the main application, MCP server, CLI, and adapter traces.
  • Common Failure Modes: Quickly identify and resolve issues like port conflicts, timeouts, and DAP protocol errors.
  • Use Case: When an AIDB session fails to initialize with an "Address already in use" error, use this skill to quickly diagnose the port conflict, identify the offending process, and apply the correct lsof and kill commands to free up the port.

Quick Start

My AIDB session is timing out. How do I check the adapter logs and enable tracing?

Frequently Asked Questions about troubleshooting

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

FAQPage Schema
How do I diagnose why my AIDB session is failing to initialize?

Follow the structured investigation workflow: reproduce the issue, check logs from the main application and CLI, enable adapter tracing, and identify common failure modes like port conflicts or timeouts. The troubleshooting skill provides step-by-step playbooks and diagnostic commands for each component.

Where do I find logs for AIDB debugging across different environments?

Log locations vary by component: main application logs, MCP server traces, CLI output, and adapter-specific logs. This skill maps exact log paths for each, plus environment variables to enable debug-level tracing in CLI, test, CI/CD, and adapter contexts.

What are common AIDB errors and how do I fix them?

Common failure modes include port conflicts, connection timeouts, and DAP protocol errors. The skill identifies each pattern, explains the root cause, and provides corrective diagnostic commands like `lsof` and environment adjustments to resolve issues quickly.

How do I enable tracing and capture diagnostic output from AIDB adapters?

Enable tracing by setting environment variables and running diagnostic command playbooks specific to your adapter. The skill guides you through reproduction, log capture, error pattern matching, and validation across adapters, test environments, and CI/CD workflows.

Can I use this troubleshooting approach with AIDB across different platforms and test setups?

Yes. The structured investigation workflows and diagnostic playbooks apply across adapters, local CLI usage, test environments, CI/CD pipelines, and MCP servers, with component-specific routing to specialized skills for deeper resolution.