cf-fix

/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.

Fix the bug: $ARGUMENTS

Workflow

Step 0: Custom Guide

bash "<plugin-root>/lib/load-custom-guide.sh" cf-fix

If output is not empty: ## Before → before first step, ## Rules → throughout, ## After → after final step.

Step 1: Understand the Bug

1. Read the error or description from $ARGUMENTS
2. If unclear, ask expected vs actual, and when it happens

Step 2: Verify the Problem Exists

1. Run the failing test or command; capture exact output
2. If you cannot reproduce, tell the user and ask for context — do NOT guess
3. No test AND --add-tests (alias --tdd) → write one that fails. Else reproduce via existing tests or by running the code.

Step 3: Recall Past Bugs + Explore Relevant Code

3a. Check existing bug docs (memory recall):

Extract 2–3 keywords from the bug.

Primary — Memory MCP (if memory_search is available): { "query": "<bug keywords>", "type": "episode", "limit": 3 }

Fallback — grep ({docsDir} from .coding-friend/config.json, default docs):

1. Grep ^description: in {docsDir}/memory/bugs/**/*.md
2. Else grep ^tags:

Read the top 1–2 matches; pass relevant findings to the explorer.

3b. Generate task-id and explore (cf-explorer):

1. task-id: YYYY-MM-DD-<short-descriptor>
2. docsDir: .coding-friend/config.json or docs
3. Context file: {docsDir}/context/{task-id}.json

Call invoke_subagent with agent cf-explorer. Pass:

Diagnose this bug: [from $ARGUMENTS] Error output: [Step 2] Context file: write structured findings to [docsDir/context/.json] [If 3a hits]: Related past bugs: [summary] Answer: (1) error path backward to origin (2) files/functions/deps (3) existing tests (4) relevant patterns