fix-issuelisted

# /fix-issue [issue-number or description] Structured workflow for investigating and fixing a reported bug or GitHub issue. ## Usage ``` /fix-issue 42 # Fix GitHub issue #42 (reads via gh CLI) /fix-issue "auth fails on logout" # Fix by description /fix-issue # Fix current known bug (from CONTEXT_STATE.md) ``` ## Workflow ### 1. Understand the Issue If issue number provided: ```bash gh issue view <number> ``` Otherwise, read description from the prompt or CONTEXT_STATE.md. Extract: - **Expected** behavior - **Actual** behavior - **Reproduction steps** - **Affected files** (if known) ### 2. Search for Root Cause **KG-first**: `search_knowledge_graph("error description or symptom")` **Code graph**: `search_code_graph("function or component name")` **Then Grep**: for exact error messages, function names, stack traces ### 3. Reproduce the Bug Run existing tests to confirm failure: ```bash pytest tests/ -k "relevant_test" -v ``` If no existing test covers it, write a failing test first (TDD approach). ### 4. Identify Root Cause Read the relevant files. Trace the execution path. Document root cause in 1-2 sentences before writing any fix. ### 5. Implement the Fix - Minimal change — don't refactor surrounding code - No new behavior beyond what's needed for the fix - Keep diff small and focused ### 6. Add Regression Test - If a failing test was written in step 3, ensure it now passes - If no test existed, add one that would