fix

name	fix
description	Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document
argument-hint	[ISS-NNN or bug description]

Fix the bug: $ARGUMENTS

Workflow

0. Check Tracking + Memory

• Check auto-memory for prior lessons matching this bug type
• Read ISSUES.md — find the relevant tracked issue by ID or description
• If the issue isn't tracked yet, add it to ISSUES.md first (assign next ISS-NNN ID)
• Update issue status to IN PROGRESS

1. Verify the Issue Exists

• Read the code at the reported location
• Confirm the bug is real, not a false alarm
• If already fixed or no longer applies: update ISSUES.md status to FIXED and stop

2. Root-Cause Analysis

1. Read the code — understand what it does, not what you think it does
2. Trace the data flow — for tool issues: schema → handler → endpoint → request → response
3. Never stop at the first failure — ask "why did THIS fail?" and trace backward
4. Check Known Patterns & Pitfalls in CLAUDE.md — is this a known pattern?

3. Implement the Fix

• Fix the root cause — not the symptom
• Minimal change — don't refactor surrounding code
• Follow the project's conventions (CLAUDE.md)
• If the fix changes tool behavior or params, note what docs need updating