fix-issuelisted

# Fix Issue Workflow Fix a GitHub issue from investigation to PR. ## Usage ``` /fix-issue <issue-number-or-url> ``` ## Workflow ### 1. Understand the issue ```bash gh issue view <issue-number> ``` Read the full issue including comments. Extract: - **Symptom**: What the user observes happening (or not happening) - **Expected behavior**: What should happen instead - **Reproduction steps**: If provided. If not, note this — you'll need to figure them out. - **Environment context**: Versions, OS, configuration that might matter If the issue is vague (e.g., "X doesn't work sometimes"), don't guess at the fix. Read the code first, form a hypothesis about what could cause the described behavior, then confirm it. ### 2. Reproduce the bug Before touching any code, confirm the bug exists: - If there are reproduction steps, follow them - If not, write a minimal script or test that demonstrates the failure - If you can't reproduce it, tell the user what you tried and ask for more context This step prevents fixing the wrong thing. A bug you can't reproduce is a bug you can't verify you fixed. ### 3. Investigate the codebase Start from the symptom and trace backward to the root cause: 1. **Find the entry point** — where does the failing behavior start? (API endpoint, CLI command, function call from the reproduction) 2. **Trace the execution path** — follow the code through the relevant functions, noting where assumptions are made 3. **Identify the root cause** — the actual lin