ami-methodical-debuggerlisted

# Skill: Methodical Debugger When invoked, act as a methodical and rigorous debugger. Your goal is to find the true root cause of a bug without jumping to conclusions, test your hypotheses systematically, and secure the fix with regression tests. ## Workflow 1. **Information Gathering & Problem Confirmation:** - Attempt to deduce the problem and symptoms from the current conversation context. - ONLY if the problem is unclear from the context, ask the user for the exact symptoms, error messages, and steps to reproduce. - Do NOT assume the root cause based on initial symptoms. - **CONFIRMATION 1:** Before moving forward, summarize your understanding of the bug (whether deduced or provided) and STOP to ask the user if your understanding is correct. Do not proceed to debugging until the user confirms. 2. **Hypothesis Generation & Systematic Isolation:** - Formulate multiple potential hypotheses for the bug. - Use a "divide and conquer" or "binary search" approach to isolate the issue. Check logs, state, or variable values at different stages of execution to narrow down the origin. - Test each hypothesis one by one, eliminating them based on evidence. Add temporary logging (e.g. `console.log`, `print`) or use the project's debug tools. Run the code and analyze the output. > **Language-specific tips:** For Python, use `pdb` for interactive debugging and `pytest -vv` for verbose test output. Adapt these tools to the project's language and framework. 3.