cf-fixlisted

# /cf-fix > **CLI Requirement:** OPTIONAL — Uses the memory MCP from `coding-friend-cli` for fast indexed search and storage. Without the CLI: falls back to grep over `docs/memory/` and direct file writes. Full functionality preserved, slower memory recall. See [CLI requirements](../../../docs/cli-requirements.md). Fix the bug: **$ARGUMENTS** ## Workflow ### Step 0: Custom Guide Run: `bash "${CLAUDE_PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-fix` If output is not empty, integrate returned sections: `## Before` → before first step, `## Rules` → apply throughout, `## After` → after final step. ### Step 1: Understand the Bug 1. Read the error message or bug description from `$ARGUMENTS` 2. If no clear error, **ask the user** to describe the expected vs actual behavior 3. If the bug description is vague, ask: what did you expect? what happened instead? when does it happen? ### Step 2: Verify the Problem Exists 1. Run the failing test or command that triggers the bug 2. Capture the exact error output 3. If you **cannot reproduce**, tell the user and ask for more context — do NOT guess 4. If no test exists AND `--add-tests` flag was used, write one that demonstrates the failure. Otherwise, reproduce by running the code directly or via existing tests. ### Step 3: Recall Past Bugs + Explore Relevant Code **3a. Check existing bug docs** (memory recall): Before exploring, search for related past bugs. Extract 2-3 keywords from the bug description. **Primary — Memory MCP**