debuglisted

# Debug Mode **Recommended model tier:** smart (opus) - this skill requires complex reasoning Systematic approach to identifying and fixing bugs. ## Prerequisites Before starting: - Get the exact error message or unexpected behavior description - Identify the entry point or trigger for the bug - Note any relevant environment details (Node version, OS, etc.) ## Workflow ### Step 1: Reproduce the Issue **Goal:** Confirm the bug exists and understand its behavior. ```bash # Run the failing code/test npm test -- --grep "failing test" # OR node path/to/script.js ``` Document: - Exact error message - Steps to trigger - Expected vs actual behavior - Is it consistent or intermittent? **If cannot reproduce:** - Check environment differences - Look for race conditions - Check for cached state ### Step 2: Locate the Relevant Code Use tools to find code related to the error: ``` # Search for function mentioned in stack trace mcp__plugin_aide_aide__code_search query="functionName" kind="function" # Get a structural overview of the suspect file (signatures + line ranges) mcp__plugin_aide_aide__code_outline file="path/to/file.ts" # Get symbols in suspect file mcp__plugin_aide_aide__code_symbols file="path/to/file.ts" # Search for error message text in code Grep for "error message text" ``` ### Step 3: Trace the Execution Path Follow the code flow from entry to error: 1. Use `code_outline` on each file in the call chain to understand its structure 2. Use `code_reference